- Notifications
You must be signed in to change notification settings - Fork2.6k
fix(core): handle nx config in package.json in move generator#30270
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
vercelbot commentedMar 5, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
The latest updates on your projects. Learn more aboutVercel for Git ↗︎ 1 Skipped Deployment
|
nx-cloudbot commentedMar 5, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
View yourCI Pipeline Execution ↗ for commite21db83.
☁️Nx Cloud last updated this comment at |
e4f7e56
intomasterUh oh!
There was an error while loading.Please reload this page.
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. |
Current Behavior
When the Nx configuration is in
package.json#nx
and not inproject.json
, the move generator creates aproject.json
file in the new destination.Expected Behavior
When the Nx configuration is in
package.json#nx
and not inproject.json
, the move generator should not create aproject.json
file in the new destination and should update thenx
entry in thepackage.json
file.Related Issue(s)
Fixes #