Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add 'project:' dependencies #59

Closed
wants to merge 1 commit into from
Closed

Conversation

ntkoopman
Copy link

Yet another proposal for working with a monorepo: Add a project: dependency option, which will resolve tarball packages against the project root instead of the current directory.

@ntkoopman
Copy link
Author

A proof of concept implementation is available at yarnpkg/yarn#3281

Allows specifying a .tgz file as a project dependency. These will be
resolved against the workspace directory (a parent directory containing
a .yarn.workspace file) instead of the current directory.
@ntkoopman
Copy link
Author

After using this for a couple of days it is obvious that storing the hash in the lockfile will lead to lots of potential merge conflicts.

@bestander
Copy link
Member

Hey, @ntkoopman, thanks for a very insightful analysis.
What do you think of workspaces #60 and knit command #41 RFC?

We started working on a solution to address monorepo dependency management from different angles and as a whole.
And in my RFC I highlighted phase 3 #60 which I think is related to what you are trying to solve here.
Do you want to help with that?

@cpojer
Copy link

cpojer commented Jun 1, 2017

Closing as this is solved by workspaces/yarn knit.

@cpojer cpojer closed this Jun 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants