Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
There's currently no good way to install a local project as a lib in another local project.
See this Discord conversation
And provides a better workflow for: #5099
Implementation notes
lib.install.localbranch.squashbut from a different local project into the current lib.I installed foo as bar.->I installed foo into lib.bar; IMO it's a little clearer where to look for things after they're installed, but happy to change it if others feel differently.Interesting/controversial decisions
The controversial thing I could think of is if we just want to do something better, but that's a big design space and I think it's worth having this very practical fix in the meantime :)
Also, I didn't add any sort of checks for any existing lib that may be overwritten by a
lib.install.local, I wanted it to be low friction when iterating on local deps a lot, and figure the user can always just undo if needed.Test coverage
Added transcripts
Loose ends
I'd love to have some sort of local sym-link support or something, but that's a bigger separate discussion.