[chore] Add script to symlink dependencies from monorepo to project #254
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bjoerge
pushed a commit
that referenced
this pull request
Oct 11, 2017
bjoerge
pushed a commit
that referenced
this pull request
Oct 11, 2017
bjoerge
pushed a commit
that referenced
this pull request
Oct 12, 2017
bjoerge
pushed a commit
that referenced
this pull request
Oct 12, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Background: Sometimes I find the need to test the latest changes in the monorepo against a specific Sanity project, and symlinking the whole
@sanityfolder isn't a good solution because it "installs" dependencies that aren't really part of the equation. It also doesn't include plugins outside of the@sanityscope.Solution: This PR adds a script that can be called from a project directory to replace the installed and declared packages with the ones from the monorepo. All packages that exist in the monorepo are first removed from
node_modulesin the given directory (to make up for hoisting shared dependencies). Then, each of the packages declared inpackage.jsonare symlinked from the monorepo intonode_modulesdirectly. Once this is done, it's up to the developer to make sure compiled versions are available usingnpm run watchornpm run buildin the monorepo.