fix: handle npm v7 overwriting node_modules
symlink
#636
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.
context: #633
The issue was that npm v7 (enabled in
@vercel/build-utils
v2.12.0 by vercel/vercel#6532) apparently refuses to install into a symlinkednode_modules
folder so dev dependencies were being added to the lambda.This PR re-upgrades to the latest build-utils and adds a workaround for this npm behaviour.