这是indexloc提供的服务,不要输入任何密码
Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion examples/non-monorepo/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@
},
"devDependencies": {
"@eslint/eslintrc": "^3.3.1",
"@types/node": "^22.15.30",
"@types/node": "^24.7.2",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"@types/node": "^24.7.2",
"@types/node": "^22.15.30",

The @types/node version ^24.7.2 is invalid because Node.js version 24 doesn't exist yet. This should likely be ^22.15.31 or another valid v22 version.

View Details

Analysis

package.json and pnpm-lock.yaml mismatch for @types/node in examples/non-monorepo

What fails: The examples/non-monorepo/package.json specifies @types/node@^24.7.2 but examples/non-monorepo/pnpm-lock.yaml has @types/node@^22.15.30 with version 22.15.31 installed.

How to reproduce:

cd examples/non-monorepo
grep "@types/node" package.json     # Shows: "^24.7.2"
grep -A2 "'@types/node':" pnpm-lock.yaml  # Shows specifier: ^22.15.30, version: 22.15.31

Result: Mismatch between package.json and lockfile. While @types/node@24.7.2 exists (Node.js 24 was released May 2025), this was introduced by dependabot commit bd2796bfd which only updated package.json without updating the lockfile.

Expected: package.json and lockfile should be in sync. Rolled back to ^22.15.30 to match the lockfile and align with other examples in the repository (which use v20 or v22). Node.js 22 is Active LTS, while Node.js 24 is Current (not LTS yet).

"@types/react": "^19.1.6",
"@types/react-dom": "^19.1.6",
"eslint": "^9.33.0",
Expand Down
Loading