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
{{ message }}
Repository navigation
Prune the react-native tree from the published shrinkwrap #1962
The registry-install half of #1937.alasql's optional react-native-fs dependency peer-depends on react-native, which npm auto-installs — ~140MB and ~200 packages of code unreachable under Node. The published 5.1.23 shrinkwrap pins 794 packages, 64 of them react-native/hermes/metro.Strip the subtree from the shrinkwrap that ships in the published package, alongside the existing dev prune (#1783). npm honours overrides only for the root project, so they cannot help a consumer; the published shrinkwrap is authoritative for registry installs, which makes it the lever that actually reaches users — no stub package or third-party empty module needed.Covers npm install harper from the registry. The Docker image is not covered: it installs from a local tarball, which has no packument, so npm never learns the shrinkwrap exists. That is #1960.Fixed by #1959.
Activity