Closed Panaith closed 1 month ago
Thanks for reporting this!
From which Nx version are you migrating from? It looks like the package.json
you shared was the final one after running nx migrate latest
. Could you provide the initial state instead?
I updated the package.json
information in the main post, so that is not misleading anymore (sorry for that).
The provided package.json
now is the initial state of the app.
Thanks for the updated package.json
!
Unfortunately, I still couldn't reproduce the issue. Based on the provided information, I tried the following:
dependencies
and devDependencies
with the provided package.json
onesnpx nx migrate latest
npx nx migrate --run-migrations
The migrations ran successfully. You can see the output logs by expanding the section below:
I also used a similar environment to the one you reported:
Node : 20.11.1
OS : win32-x64
npm : 10.2.4
You can try running with the --verbose
flag to see if there's any extra information that can help, but we'll most likely need a repo where the issue can be reproduced so we can troubleshoot it.
This issue has been automatically marked as stale because more information has not been provided within 7 days. It will be closed in 21 days if no information is provided. If information has been provided, please reply to keep it active. Thanks for being a part of the Nx community! 🙏
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behavior
npx nx migrate latest
npx nx migrate --run-migrations
Expected Behavior
Running normally
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
The
npm WARN EBADENGINE Unsupported engine {.....
warnings are due to node version 20.11.0, running the same with node version 20.15.0 does not give these warnings but still gives the same Failure logs.my package.json file is: