2.0.0-rc.6 | Clean project install results in 'npm error ERESOLVE could not resolve'

[karimmaassen]

Steps I took

% npm init solid@latest

> npx
> 'create-solid'


┌  
 Create-Solid v0.12.0
│
◇  Project Name
│  .
│
◇  What type of project would you like to 
│  create?
│  Solid 2.0 (RC)
│
◇  Use Typescript?
│  No
│
◇  Which template would you like to use?
│  with-tailwindcss
│
◇  Add @solidjs/start-devtools (development 
│  toolbar)?
│  Yes
│
◇  Project created 🎉
│
◇  To get started, run: ─╮
│                        │
│  npm install           │
│  npm run dev           │
│                        │
├────────────────────────╯

Then I install the dependencies:

% npm i

And get the following errors:

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @solidjs/vite-plugin@3.0.0-next.41
npm error Found: @testing-library/jest-dom@7.0.1
npm error node_modules/@testing-library/jest-dom
npm error   dev @testing-library/jest-dom@"^7.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @testing-library/jest-dom@"^5.16.6 || ^5.17.0 || ^6.*" from @solidjs/vite-plugin@3.0.0-next.41
npm error node_modules/@solidjs/vite-plugin
npm error   dev @solidjs/vite-plugin@"^3.0.0-next.38" from the root project
npm error
npm error Conflicting peer dependency: @testing-library/jest-dom@6.9.1
npm error node_modules/@testing-library/jest-dom
npm error   peerOptional @testing-library/jest-dom@"^5.16.6 || ^5.17.0 || ^6.*" from @solidjs/vite-plugin@3.0.0-next.41
npm error   node_modules/@solidjs/vite-plugin
npm error     dev @solidjs/vite-plugin@"^3.0.0-next.38" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error

Environment

Mac Tahoe 26.6.2
node v24.21.0
npm 11.19.0

Install package

{
  "name": "example-with-tailwindcss",
  "version": "0.0.0",
  "description": "",
  "type": "module",
  "scripts": {
    "start": "vite",
    "dev": "vite",
    "build": "vite build",
    "serve": "vite preview",
    "test": "vitest",
    "lint": "oxlint src"
  },
  "license": "MIT",
  "devDependencies": {
    "@solidjs/diagnostics": "^2.0.0-rc.6",
    "@solidjs/start-devtools": "^1.0.0-next.4",
    "@solidjs/testing-library": "^1.0.0-beta.3",
    "@solidjs/vite-plugin": "^3.0.0-next.38",
    "@tailwindcss/vite": "^4.1.13",
    "@testing-library/jest-dom": "^7.0.0",
    "eslint-plugin-solid": "~0.18.0",
    "filesystem-routing": "0.2.1",
    "jsdom": "^25.0.1",
    "oxlint": "~1.79.0",
    "tailwindcss": "^4.1.13",
    "typescript": "^5.9.2",
    "vite": "^8.1.5",
    "vitest": "^5.0.0"
  },
  "dependencies": {
    "@solidjs/meta": "^1.0.0-next.2",
    "@solidjs/router": "^2.0.0-next.21",
    "@solidjs/web": "^2.0.0-rc.6",
    "solid-js": "^2.0.0-rc.6"
  }
}

[ryansolid]

Thanks for the clean report — confirmed, and it's not the templates or core, it's a stale peer range in @solidjs/vite-plugin.

@solidjs/vite-plugin@3.0.0-next.41 declares peerOptional @testing-library/jest-dom: "^5.16.6 || ^5.17.0 || ^6.*", while the Solid 2.0 templates moved to @testing-library/jest-dom@^7.0.0. npm enforces peer ranges (pnpm only warns, which is how this slipped through). The range was already widened for v7 on the plugin's 2.x line (solidjs/solid-vite-plugin#287) but never ported to the next line the 2.0 templates use.

Fix: solidjs/solid-vite-plugin#358. No code change was needed — v7 keeps the @testing-library/jest-dom/vitest subpath the plugin auto-injects — so it's purely the peer range. Verified against a fresh with-tailwindcss project under npm 11: npm install succeeds with jest-dom 7.0.1 and the template's vitest run passes.

Until the next 3.0.0-next.x publishes, npm i --legacy-peer-deps is safe here: the resolution npm is refusing (jest-dom 7 alongside the plugin) is exactly the one the PR declares as supported.

— Claude via Cursor

[ryansolid]

Fixed in @solidjs/vite-plugin@3.0.0-next.42 (solidjs/solid-vite-plugin#358): the optional @testing-library/jest-dom peer range now includes v7, which is what the Solid 2.0 templates ship. The templates use a caret range on the plugin, so a fresh npm init solid@latest + npm install picks up next.42 with no template change needed. If you already scaffolded, npm install again (or delete node_modules/package-lock.json first).

[karimmaassen]

I can confirm this has resolved the issue.