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 packages/eslint-config-sdk/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@
"@sentry/eslint-plugin-sdk": "11.10.0",
"@sentry/typescript": "11.10.0",
"@typescript-eslint/eslint-plugin": "^5.62.0",
"@typescript-eslint/parser": "^5.62.0",
"@typescript-eslint/parser": "^8.72.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.

Parser and plugin versions mismatch

High Severity

@typescript-eslint/parser is bumped to v8 while @typescript-eslint/eslint-plugin stays on v5. Those packages must share a major version, and the plugin still peers on parser ^5.0.0. The v8 parser dropped AST fields the v5 plugin reads, so type-aware rules in this published config can crash or silently miss issues.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 17525de. Configure here.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Parser incompatible with TypeScript 7

High Severity

@typescript-eslint/parser 8.72.0 requires TypeScript >=4.8.4 <6.1.0, but the lockfile resolves it against typescript@7.0.2. Parser 8 crashes on TypeScript 7 because ts.Extension was removed, typically as TypeError: Cannot read properties of undefined (reading 'Cjs') when the parser loads.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 17525de. Configure here.

"eslint-config-prettier": "^9.1.0",
"eslint-plugin-deprecation": "^3.0.0",
"eslint-plugin-import": "^2.32.0",
Expand Down
167 changes: 102 additions & 65 deletions pnpm-lock.yaml

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

Loading