You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was noticed in #218923, but when building a workspace package with buildNpmPackage and there exist dependencies in the top-level packages.json, the npm prune step does not remove those dependencies even when they are unnecessary for the specific workspace being built. This led to the store path increasing in size significantly for the derivation in #218923
I'm not 100% certain if this is a bug or not, but I'm opening an issue here to track my investigation (i.e. so that I can add it to our project board)
The text was updated successfully, but these errors were encountered:
Describe the bug
This was noticed in #218923, but when building a workspace package with
buildNpmPackage
and there exist dependencies in the top-levelpackages.json
, thenpm prune
step does not remove those dependencies even when they are unnecessary for the specific workspace being built. This led to the store path increasing in size significantly for the derivation in #218923I'm not 100% certain if this is a bug or not, but I'm opening an issue here to track my investigation (i.e. so that I can add it to our project board)
The text was updated successfully, but these errors were encountered: