fix npm prepare when node env is set to production#7805
Conversation
Overall package sizeSelf size: 4.97 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.0.0 | 81.15 kB | 815.98 kB | | dc-polyfill | 0.1.10 | 26.73 kB | 26.73 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #7805 +/- ##
===========================================
+ Coverage 70.06% 80.23% +10.17%
===========================================
Files 706 748 +42
Lines 30237 32404 +2167
===========================================
+ Hits 21185 26000 +4815
+ Misses 9052 6404 -2648 Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
BenchmarksBenchmark execution time: 2026-03-17 13:56:55 Comparing candidate commit a526c94 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 232 metrics, 28 unstable metrics. |
rochdev
force-pushed
the
fix-npm-prepare-node-env
branch
from
6983fa3 to
a526c94
Compare
2 participants
What does this PR do?
Fix npm prepare when NODE_ENV is set to production.
Motivation
The prepare script runs a new install in a subfolder which always requires dev dependencies to be present to work.
Additional Notes
Technically this means they are prod dependencies, but keeping them as dev dependencies provides a clear distinction with the dependencies that will be vendored.