-
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
feat(misc): change updateBuildableProjectDepsInPackageJson option default value to false #17920
feat(misc): change updateBuildableProjectDepsInPackageJson option default value to false #17920
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 63faf43. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
78ca70a
to
dde4266
Compare
dde4266
to
0625c19
Compare
0625c19
to
90a0b4e
Compare
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 fine from docs perspective
…ault value to false
90a0b4e
to
63faf43
Compare
packages/js/src/migrations/update-16-6-0/explicitly-set-projects-to-update-buildable-deps.ts
Show resolved
Hide resolved
packages/js/src/migrations/update-16-6-0/explicitly-set-projects-to-update-buildable-deps.ts
Show resolved
Hide resolved
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. |
This is the first step to moving from using the current package.json generation in executors to using the new
@nx/dependency-checks
EsLint rule instead. In a follow-up PR, the options will be deprecated.The PR comes with migrations for targets using the relevant executors and are relying on the default value for the
updateBuildableProjectDepsInPackageJson
. In those cases, the option will be explicitly set totrue
in the target configuration to keep the existing behavior.Current Behavior
The
updateBuildableProjectDepsInPackageJson
option of several executors has a default value oftrue
.Expected Behavior
The
updateBuildableProjectDepsInPackageJson
option of several executors should have a default value offalse
.Related Issue(s)
Fixes #