Skip to content
Open
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 @@ -54,7 +54,7 @@
"@typescript-eslint/eslint-plugin": "^7.13.0",
"@typescript-eslint/parser": "^7.13.0",
"cz-conventional-changelog": "^3.3.0",
"eslint": "^8.57.1",
"eslint": "^10.0.2",
Copy link

Choose a reason for hiding this comment

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

Bug: The package.json scripts use the --ext flag with eslint, but this flag was removed in the newly upgraded ESLint v10, which will cause script failures.
Severity: CRITICAL

Suggested Fix

Remove the --ext flag from all eslint commands in the package.json scripts. Create a new eslint.config.js flat configuration file to specify which files ESLint should process, replacing the functionality previously handled by the --ext flag.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L57

Potential issue: The project has been upgraded to ESLint v10, which removes support for
the `--ext` command-line flag. However, the `test`, `lint`, and `lint-staged` scripts in
`package.json` still use the `--ext` flag. This will cause these scripts to fail at
runtime with an "Invalid option '--ext'" error, breaking local development and CI
workflows like testing, linting, and committing code.

"eslint-config-prettier": "^10.1.5",
"eslint-plugin-prettier": "^5.2.6",
"lint-staged": "^16.1.0",
Expand Down
Loading
Loading