Failed to run 'npm install' following migration from 20.4.0 to 20.4.1

[n-mcnally]

Current Behavior

After running npx nx migrate latest to update to 20.4.1 (from 20.4.0) running npm install failed with a resolution error.

Expected Behavior

Should successfully install following migration.

GitHub Repo

No response

Steps to Reproduce

1. Run npx nx migrate latest and then try to install following migration.

Nx Report

Unable to run

Failure Logs

# npm resolution error report

While resolving: @nx/playwright@20.4.1
Found: @nx/vite@20.4.1
node_modules/@nx/vite
  dev @nx/vite@"20.4.1" from the root project

Could not resolve dependency:
peerOptional @nx/vite@"file:../vite" from @nx/playwright@20.4.1
node_modules/@nx/playwright
  dev @nx/playwright@"20.4.1" from the root project

Conflicting peer dependency: @nx/vite@undefined
node_modules/@nx/vite
  peerOptional @nx/vite@"file:../vite" from @nx/playwright@20.4.1
  node_modules/@nx/playwright
    dev @nx/playwright@"20.4.1" from the root project

Fix the upstream dependency conflict, or retry
this command with --force or --legacy-peer-deps
to accept an incorrect (and potentially broken) dependency resolution.

Any the related nx devDependencies are:

{
    "@nx/eslint": "20.4.1",
    "@nx/eslint-plugin": "20.4.1",
    "@nx/js": "20.4.1",
    "@nx/playwright": "20.4.1",
    "@nx/react": "20.4.1",
    "@nx/vite": "20.4.1",
    "@nx/web": "20.4.1",
    "@nx/workspace": "20.4.1",
    "vite": "^5.0.0",
    "vitest": "^2.1.8",
    // ...
}

Package Manager Version

npm 11.0.0

Operating System

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

Additional Information

No response

[masonmark]

I got the same thing updating to 20.4.1. If using npm one fairly targeted way to work around this is to add this to your package.json file:

  "overrides": {
    "@nx/playwright@20.4.1": {
      "@nx/vite": "20.4.1"
    }
  },

(If using pnpm or yarn IIRC the equivalent feature is called resolutions.)

That forces the @nx/vite package to version "20.4.1" but only for the @nx/playwright@20.4.1" package, so it shouldn't affect the rest of your dependency graph. I expect this is a packaging error that will be fixed in 20.4.2...

Update

In our case, I had to also add the same workaround for @nx/webpack:

  "overrides": {
    "@nx/playwright@20.4.1": {
      "@nx/vite": "20.4.1",
      "@nx/webpack": "20.4.1"
    }
  },

[FrozenPandaz]

That's not right. @AgentEnder can you take a look into this please?