Migration to v14 fails
See original GitHub issueCurrent Behavior
Migrating to v14.0.5
fails with the error pasted below.
Expected Behavior
Migrating from previous versions worked.
Steps to Reproduce
The issue happens when migrating from 13.10.2
to any other version, including the latest one 14.0.5
but also 13.10.3
.
Failure Logs
error https://registry.yarnpkg.com/acorn/-/acorn-8.7.1.tgz: Extracting tar content of undefined failed, the file appears to be corrupt: "ENOENT: no such file or directory, stat 'C:\\src\\yarn\\v6\\npm-acorn-8.7.1-0197122c843d1bf6d0a5e83220a788f278f63c30-integrity\\node_modules\\acorn\\dist\\acorn.mjs'"
Environment
Node : 16.13.1
OS : win32 x64
yarn : 1.22.18
nx : 13.10.2
@nrwl/angular : Not Found
@nrwl/cypress : 13.10.2
@nrwl/detox : Not Found
@nrwl/devkit : 13.10.2
@nrwl/eslint-plugin-nx : 13.10.2
@nrwl/express : Not Found
@nrwl/jest : 13.10.2
@nrwl/js : 13.10.2
@nrwl/linter : 13.10.2
@nrwl/nest : Not Found
@nrwl/next : 13.10.2
@nrwl/node : 13.10.2
@nrwl/nx-cloud : Not Found
@nrwl/nx-plugin : Not Found
@nrwl/react : 13.10.2
@nrwl/react-native : Not Found
@nrwl/schematics : Not Found
@nrwl/storybook : 13.10.2
@nrwl/web : 13.10.2
@nrwl/workspace : 13.10.2
typescript : 4.6.4
rxjs : 6.6.6
---------------------------------------
Community plugins:
@jscutlery/semver: 2.23.3
Issue Analytics
- State:
- Created a year ago
- Reactions:2
- Comments:11 (1 by maintainers)
Top Results From Across the Web
Failed Upgrade from v13.12.15 to v14 - GitLab Forum
Hi,. I am trying to upgrade from version 13.12.15 to version 14. According to the upgrade path, I can upgrade to 14.0.12.
Read more >Step 7 v5.5 migration to TIA PORTAL v14 error [ HELP ME ...
Hi, I encounter error when trying to migrate the v5.5 project as follows: Module 2AI RTD ST (6ES7 134-4JB50-0AB0) in slot 2 cannot...
Read more >CMCNE migration failed from v14.2.2 to v14.4.4 | Dell Canada
From Migration failure logs, below RAM space issue was reported under cw log file which was stopping the migration to CMCNE v14.4.4:
Read more >Migrating from v13 to fresh v14 installation ... - ERPNext Forum
Migrating from v13 to fresh v14 installation, bench migrate command throws up an error where it expects a doctype present in HRMS ·...
Read more >TRAC 1.0.2 Migration to v14 - Error (No Trac environment found)
#2 Mercurial (hg) is no longer supported in the current appliance, so that explains why that is not working. #3 My guess is...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This worked for me finally, and I had upgraded to pnpm v7 also…
npm migrate
script =nx migrate --run-migrations
pnpm i
pnpm add nx
pnpm run migrate
Now I feel not all that is actually necessary and likely can be condensed down, but it’s exactly what I stumbled so figured I’d share. Now that I’m good for now, unfortunately don’t have the time to test what’s the important bit. I’d guess something around the new un-namespaced
nx
package.UPDATE: I am able to migrate to latest version, when I execute the above in “Command Prompt” with Administrative rights. Now, experiencing errors in react testing library, it could be because of the latest migration updated the react version to v18.