Unable to use nx migrate ** cli command

[nielslindeboom]

Current Behavior

Im facing an issue when i use the cli command nx migrate latest
I used nvm to manage my node runtimes

Expected Behavior

Able to run the cli command

GitHub Repo

No response

Steps to Reproduce

Install a clean workspace using npx create-nx-workspace@latest or version specific

Once installed

I attempt to run nx migrate latest i get a spawn npm ENOENT error

Nx Report

Node           : 22.19.0
OS             : win32-x64
Native Target  : x86_64-windows
npm            : 10.9.3

nx                     : 21.5.2
@nx/js                 : 21.5.2
@nx/eslint             : 21.5.2
@nx/workspace          : 21.5.2
@nx/angular            : 21.5.2
@nx/devkit             : 21.5.2
@nx/eslint-plugin      : 21.5.2
@nx/module-federation  : 21.5.2
@nx/rspack             : 21.5.2
@nx/web                : 21.5.2
@nx/webpack            : 21.5.2
typescript             : 5.9.2
---------------------------------------
Community plugins:
angular-eslint : 20.2.0
---------------------------------------
Cache Usage: 0.00 B / 95.16 GB

Failure Logs

Error: spawn npm ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:285:19)
    at onErrorNT (node:internal/child_process:483:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn npm',
  path: 'npm',
  spawnargs: [ 'view', 'nx@latest', '--json', '--silent' ],
  cmd: 'npm view nx@latest --json --silent',
  stdout: '',
  stderr: ''
}

Package Manager Version

No response

Operating System

• macOS
• Linux
• Windows
• Other (Please specify)

Additional Information

No response

[samlanzz]

I am currently also unable to use nx migrate. I don't get the same error, but the problem might be related?

nx migrate 21.5.1
Fetching meta data about packages.
It may take a few minutes.
Fetching nx@21.5.1

NX The migrate command failed.

NX An error occurred while checking the provenance of nx@21.5.1. This could indicate a security risk. Please double check https://www.npmjs.com/package/nx to see if the package is published correctly or file an issue at https://github.com/nrwl/nx/issues

Error: No attestation URL found

[jmajnek]

I can reproduce the same issue on my Windows machine. In WSL, it works as expected.

[JonWallsten]

Same here. But a bit different output:

nx migrate 21.5.2                        
Fetching meta data about packages.
It may take a few minutes.
Fetching nx@21.5.2

 NX   The migrate command failed.


 NX   spawn npm ENOENT

Pass --verbose to see the stacktrace.

nx migrate [packageAndVersion]

Creates a migrations file or runs migrations from the migrations file.
- Migrate packages and create migrations.json (e.g., nx migrate @nx/workspace@latest)
- Run migrations (e.g., nx migrate --run-migrations=migrations.json). Use flag --if-exists to run migrations only if the migrations file exists.

Positionals:
  packageAndVersion  The target package and version (e.g, @nx/workspace@16.0.0).                                                                                      [string]
Options:
      --help                      Show help                                                                                                                          [boolean]      
      --version                   Show version number                                                                                                                [boolean]      
      --verbose                   Prints additional information about the commands (e.g., stack traces).                                                             [boolean]      
      --runMigrations             Execute migrations from a file (when the file isn't provided, execute migrations from migrations.json).                             [string]      
      --ifExists                  Run migrations only if the migrations file exists, if not continues successfully.                                 [boolean] [default: false]      
      --from                      Use the provided versions for packages instead of the ones installed in node_modules (e.g., 
      --from="@nx/react@16.0.0,@nx/js@16.0.0").    [string]                                                                                                                                                             
      --to                        Use the provided versions for packages instead of the ones calculated by the migrator (e.g., 
                                                                                                                                                        
      --to="@nx/react@16.0.0,@nx/js@16.0.0").[string]  -C,                                                                                                                                                          
      --createCommits             Automatically create a git commit after each migration runs.     [boolean] [default:false]      
                                                                                                                                                         --commitPrefix              Commit prefix to apply to the commit for each migration, when 
      --create-commits is enabled.      [string] [default: "chore: [nx migration] "]      
      --interactive               Enable prompts to confirm whether to collect optional package updates and migrations.                             [boolean] [default: false]      
      --excludeAppliedMigrations  Exclude migrations that should have been applied on previous updates. To be used with 
      --from.                     [boolean] [default: false]
Examples:
  migrate latest                                                           Update all Nx plugins to "latest". This will generate migrations.json
  migrate 9.0.0                                                            Update all Nx plugins to "9.0.0". This will generate migrations.json
  migrate @nx/workspace@9.0.0 --from="@nx/workspace@8.0.0,@nx/node@8.0.0"  Update @nx/workspace and generate the list of migrations starting with version 8.0.0 of
                                                                           @nx/workspace and @nx/node, regardless of what is installed locally
  migrate @nx/workspace@9.0.0 --to="@nx/react@9.0.1,@nx/angular@9.0.1"     Update @nx/workspace to "9.0.0". If it tries to update @nx/react or @nx/angular, use version       
                                                                           "9.0.1"
  migrate another-package@12.0.0                                           Update another-package to "12.0.0". This will update other packages and will generate
                                                                           migrations.json file
  migrate latest --interactive                                             Collect package updates and migrations in interactive mode. In this mode, the user will be prompted                                                                           whether to apply any optional package update and migration
  migrate latest --from=nx@14.5.0 --exclude-applied-migrations             Collect package updates and migrations starting with version 14.5.0 of "nx" (and Nx first-party    
                                                                           plugins), regardless of what is installed locally, while excluding migrations that should have been                                                                           applied on previous updates
  migrate --run-migrations=migrations.json                                 Run migrations from the provided migrations.json file. You can modify migrations.json and run this 
                                                                           command many times
  migrate --run-migrations --create-commits                                Create a dedicated commit for each successfully completed migration. You can customize the prefix  
                                                                           used for each commit by additionally setting --commit-prefix="PREFIX_HERE "

Find more information and examples at https://nx.dev/nx/migrate

Error: Command failed: C:\Users\me\AppData\Local\Temp\tmp-42348-C8wFaMoLCLcN\node_modules\.bin\nx _migrate latest
    at genericNodeError (node:internal/errors:983:15)
    at wrappedFn (node:internal/errors:537:14)
    at checkExecSyncError (node:child_process:882:11)
    at execSync (node:child_process:954:15)
    at Object.runMigration (C:\Users\me\repo\ci-web\node_modules\nx\src\command-line\migrate\migrate.js:1140:42)
    at Object.handler (C:\Users\me\repo\ci-web\node_modules\nx\src\command-line\migrate\command-object.js:13:68) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 7460,
  stdout: null,
  stderr: null
}

[simhnna]

I've also ran into Error: No attestation URL found.

I'm in a corporate setting using JFrog Artifactory as a registry. It looks like Artifactory doesn't support/pass-through the attestations which is why it's failing for us.
There probably isn't much nx can do about that, but maybe inform users that this can be a cause.

[MaxKless]

Hey! Thanks for the reports, everyone.
There are two issues at play here:

• the windows case is broken because we use execFileSync for security reasons. There, npm isn't defined so we will have to use npm.cmd instead.
• you can use an environment variable to skip the provenance check in the custom registry: NX_SKIP_PROVENANCE_CHECK. We add this information to the error message

Both are implemented in this PR: #32680

[samlanzz]

Hey! Thanks for the reports, everyone. There are two issues at play here:

• the windows case is broken because we use execFileSync for security reasons. There, npm isn't defined so we will have to use npm.cmd instead.
• you can use an environment variable to skip the provenance check in the custom registry: NX_SKIP_PROVENANCE_CHECK. We add this information to the error message

Both are implemented in this PR: #32680

Worked for me (NX_SKIP_PROVENANCE_CHECK). Thank you!

[yubinchen18]

I have same problem, what are the fix steps exactly??

 NX   The migrate command failed.


 NX   spawn npm ENOENT

Pass --verbose to see the stacktrace.

nx migrate [packageAndVersion]

Creates a migrations file or runs migrations from the migrations file.
  - Migrate packages and create migrations.json (e.g., nx migrate @nx/workspace@latest)
  - Run migrations (e.g., nx migrate --run-migrations=migrations.json). Use flag --if-exists to run migrations only if the migrations file exists.

Positionals:
  packageAndVersion  The target package and version (e.g, @nx/workspace@16.0.0).  [string]

Options:
      --help                      Show help  [boolean]
      --version                   Show version number  [boolean]
      --verbose                   Prints additional information about the commands (e.g., stack traces).  [boolean]
      --runMigrations             Execute migrations from a file (when the file isn't provided, execute migrations from migrations.json).  [string]
      --ifExists                  Run migrations only if the migrations file exists, if not continues successfully.  [boolean] [default: false]
      --from                      Use the provided versions for packages instead of the ones installed in node_modules (e.g., --from="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
      --to                        Use the provided versions for packages instead of the ones calculated by the migrator (e.g., --to="@nx/react@16.0.0,@nx/js@16.0.0").  [string]
  -C, --createCommits             Automatically create a git commit after each migration runs.  [boolean] [default: false]
      --commitPrefix              Commit prefix to apply to the commit for each migration, when --create-commits is enabled.  [string] [default: "chore: [nx migration] "]
      --interactive               Enable prompts to confirm whether to collect optional package updates and migrations.  [boolean] [default: false]
      --excludeAppliedMigrations  Exclude migrations that should have been applied on previous updates. To be used with --from.  [boolean] [default: false]

Examples:
  migrate latest                                                           Update all Nx plugins to "latest". This will generate migrations.json
  migrate 9.0.0                                                            Update all Nx plugins to "9.0.0". This will generate migrations.json
  migrate @nx/workspace@9.0.0 --from="@nx/workspace@8.0.0,@nx/node@8.0.0"  Update @nx/workspace and generate the list of migrations starting with version 8.0.0 of @nx/workspace and @nx/node, regardless of what is installed locally
  migrate @nx/workspace@9.0.0 --to="@nx/react@9.0.1,@nx/angular@9.0.1"     Update @nx/workspace to "9.0.0". If it tries to update @nx/react or @nx/angular, use version "9.0.1"
  migrate another-package@12.0.0                                           Update another-package to "12.0.0". This will update other packages and will generate migrations.json file
  migrate latest --interactive                                             Collect package updates and migrations in interactive mode. In this mode, the user will be prompted whether to apply any optional package update and migration
  migrate latest --from=nx@14.5.0 --exclude-applied-migrations             Collect package updates and migrations starting with version 14.5.0 of "nx" (and Nx first-party plugins), regardless of what is installed locally, while excluding migrations that should have been applied on previous updates
  migrate --run-migrations=migrations.json                                 Run migrations from the provided migrations.json file. You can modify migrations.json and run this command many times
  migrate --run-migrations --create-commits                                Create a dedicated commit for each successfully completed migration. You can customize the prefix used for each commit by additionally setting --commit-prefix="PREFIX_HERE "

Find more information and examples at https://nx.dev/nx/migrate

Error: Command failed: C:\Users\yubin\AppData\Local\Temp\tmp-19620-u4GvlCTcSyij\node_modules\.bin\nx _migrate latest
    at genericNodeError (node:internal/errors:985:15)
    at wrappedFn (node:internal/errors:539:14)
    at checkExecSyncError (node:child_process:924:11)
    at execSync (node:child_process:996:15)
    at Object.runMigration (C:\Users\yubin\source\repos\Starbase\Starbase.MonoFrontEnd\node_modules\nx\src\command-line\migrate\migrate.js:1156:42)
    at Object.handler (C:\Users\yubin\source\repos\Starbase\Starbase.MonoFrontEnd\node_modules\nx\src\command-line\migrate\command-object.js:13:68) {
  status: 1,
  signal: null,
  output: [ null, null, null ],
  pid: 14588,
  stdout: null,
  stderr: null
}

[nielslindeboom]

Thanks @MaxKless

Setting the env variable NX_SKIP_PROVENANCE_CHECK=true helped for now

[MaxKless]

@yubinchen18 on windows please be patient until the latest version of master is released to latest. It should be very soon

[sergidt]

Having the same issue, when updating from 21.3.9.

The @nielslindeboom solution works, but I think this shouldn't be required to migrate. Last 2 upgrades Having important issues...