Skip to content
Closed
Show file tree
Hide file tree
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 package.json
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@
"@types/react": "^19.0.0",
"@types/react-dom": "^19.0.0",
"@typescript-eslint/eslint-plugin": "^8.35.0",
"@typescript-eslint/parser": "^8.35.0",
"@typescript-eslint/parser": "^8.63.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Bump the package ESLint actually imports

With the current eslint.config.mjs, the lint path imports typescript-eslint, not the standalone @typescript-eslint/parser. Under this lockfile, typescript-eslint@8.61.1 still depends on and exports @typescript-eslint/parser@8.61.1 (pnpm-lock.yaml lines 6798-6802), so pnpm exec eslint . continues to use the old parser while this line only adds an unused top-level 8.63.0 copy. For this parser bump to take effect in the Pack lint gates, bump typescript-eslint and the plugin to 8.63.0 as well, or remove the unused direct parser dependency.

Useful? React with 👍 / 👎.

"eslint": "^9.29.0",
"eslint-config-prettier": "^9.1.0",
"eslint-plugin-react": "^7.37.4",
Expand Down
121 changes: 113 additions & 8 deletions pnpm-lock.yaml

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Loading