Skip to content

Conversation

@patinthehat
Copy link
Member

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Uncontrolled Recursion
SNYK-JS-ESLINT-15102420
  60  

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-ESLINT-15102420
@coderabbitai
Copy link

coderabbitai bot commented Jan 31, 2026

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • 🔍 Trigger a full review
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch snyk-fix-6a36d92d28237b5e6ffeeeea506dbc80

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@what-the-diff
Copy link

what-the-diff bot commented Jan 31, 2026

PR Summary

  • Updated ESLint Version
    The ESLint dependency in the package.json file was updated. This is important because, as part of our continuous improvement, we must keep our software tools, such as ESLint, up-to-date. Doing so ensures we have the latest features and security patches in our development environment, leading to more efficient and secure code. The version was bumped from 8.57.0 to 9.26.0.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 40cce82b88

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

"dts-bundle-generator": "^9.3.1",
"esbuild": "^0.23.0",
"eslint": "^8.57.0",
"eslint": "^9.26.0",

Choose a reason for hiding this comment

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

P2 Badge Add flat config or lint will fail under ESLint 9

ESLint 9 defaults to flat config and only looks for eslint.config.js|mjs|cjs (per eslint --help: “Use this configuration instead of eslint.config.js, eslint.config.mjs, or eslint.config.cjs” and “Disable look up for eslint.config.js”). This repo only has .eslintrc.js, so after this bump npm run lint/lint-staged will error out with “ESLint couldn't find an eslint.config.(js|mjs|cjs) file” (I reproduced with eslint src --ext ts,js). Unless you add an eslint.config.* or explicitly opt into legacy config, linting and hooks will fail for contributors/CI that run the scripts.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants