fix(core): handle nx config in package.json in move generator

[leosvelperez]

Current Behavior

When the Nx configuration is in package.json#nx and not in project.json, the move generator creates a project.json file in the new destination.

Expected Behavior

When the Nx configuration is in package.json#nx and not in project.json, the move generator should not create a project.json file in the new destination and should update the nx entry in the package.json file.

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Mar 5, 2025 0:02am

[nx-cloud]

View your CI Pipeline Execution ↗ for commit e21db83.

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	✅ Succeeded	7m 11s	View ↗
nx run-many -t check-imports check-commit check...	✅ Succeeded	16s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx format:check --base=e8aca...	✅ Succeeded	2s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	1s	View ↗
nx documentation	✅ Succeeded	56s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-03-05 14:01:09 UTC

[github-actions]

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.