fix(developer): adds utility script to facilitate Developer-build Lerna compatibility #3098
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.
NOTE: This is intended as a patch-PR for an issue noted in #3071. Feel free to automatically approve + merge it at any point if the patch seems acceptable.
Now that we're transitioning toward use of
lerna
for NPM dependency installs, our build scripts no longer manually create npm links. This affects the build script for Developer,npm install
would attempt to install now-listed dependencies that aren't actually npm published and/or are not yet published (eg: test builds).Since
npm install
ignores any packages that would install overnpm link
sites, simply preserving thenpm
links across anode_modules
folder wipe keeps the Developer script happy. It just takes a bit of work to actually auto-detect and preserve them.