-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(core): remove devDependencies in production build #21428
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 3e01619. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 6 targets
Sent with 💌 from NxCloud. |
b11843e
to
6b63360
Compare
packages/nx/src/plugins/js/package-json/create-package-json.spec.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
I would like to have those unit tests turned on though.
c13c4cc
to
ec5aa7e
Compare
ec5aa7e
to
92480ac
Compare
92480ac
to
980b040
Compare
Why? Why is this not made optional (or at-least make this behavior opt in?), as a lib maintainer we add dev dependencies so that
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
Moved from #17744
All credits to @robdonn.
Current Behavior
When a local package.json is loaded with a
devDependencies
property, that property's contents end up in the final outputtedpackage.json
, even whenisProduction
is set totrue
.Expected Behavior
When
isProduction
istrue
thendevDependencies
should be removed.Related Issue(s)
Fixes #