Skip to content

build(deps-dev): bump eslint from 8.57.1 to 9.22.0 #2924

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 10, 2025

Bumps eslint from 8.57.1 to 9.22.0.

Release notes

Sourced from eslint's releases.

v9.22.0

Features

  • 7ddb095 feat: Export defineConfig, globalIgnores (#19487) (Nicholas C. Zakas)

Bug Fixes

  • 19c0127 fix: improve message for no-console suggestions (#19483) (Francesco Trotta)
  • 49e624f fix: improve error message for falsy parsed JS AST (#19458) (Josh Goldberg ✨)

Documentation

  • 86c5f37 docs: Update README (GitHub Actions Bot)
  • fbdeff0 docs: Update README (GitHub Actions Bot)
  • c9e8510 docs: generate deprecation notice in TSDoc comments from rule metadata (#19461) (Francesco Trotta)
  • 2f386ad docs: replace var with const in rule examples (#19469) (Tanuj Kanti)
  • 0e688e3 docs: Update README (GitHub Actions Bot)
  • 06b596d docs: Restore the carrot to the position where the search input was lost (#19459) (Amaresh S M)

Chores

v9.21.0

Features

  • 418717f feat: introduce new deprecated types for rules (#19238) (fnx)
  • 5c5b802 feat: Add --ext CLI option (#19405) (Milos Djermanovic)

Bug Fixes

  • db5340d fix: update missing plugin message template (#19445) (Milos Djermanovic)
  • d8ffdd4 fix: do not exit process on rule crash (#19436) (Francesco Trotta)

Documentation

  • c5561ea docs: Update README (GitHub Actions Bot)
  • 80b0485 docs: replace var with let and const in rule example (#19434) (Tanuj Kanti)
  • f67d5e8 docs: Update README (GitHub Actions Bot)
  • 75afc61 docs: Update README (GitHub Actions Bot)
  • 0636cab docs: Update Eleventy from v2 to v3 (#19415) (Amaresh S M)
  • dd7d930 docs: Update README (GitHub Actions Bot)

Chores

  • a8c9a9f chore: update @eslint/eslintrc and @eslint/js (#19453) (Francesco Trotta)
  • 265e0cf chore: package.json update for @​eslint/js release (Jenkins)
  • 3401b85 test: add test for Rule.ReportDescriptor type (#19449) (Francesco Trotta)
  • e497aa7 chore: update rewrite dependencies (#19448) (Francesco Trotta)
  • dab5478 chore: better error message for missing plugin in config (#19402) (Tanuj Kanti)
  • ebfe2eb chore: set js language for bug report issue config block (#19439) (Josh Goldberg ✨)
  • 5fd211d test: processors can return subpaths (#19425) (Milos Djermanovic)

v9.20.1

Bug Fixes

... (truncated)

Changelog

Sourced from eslint's changelog.

v9.22.0 - March 7, 2025

  • 97f788b chore: upgrade @​eslint/js@​9.22.0 (#19489) (Milos Djermanovic)
  • eed409a chore: package.json update for @​eslint/js release (Jenkins)
  • f9a56d3 chore: upgrade [email protected] (#19488) (Milos Djermanovic)
  • 7ddb095 feat: Export defineConfig, globalIgnores (#19487) (Nicholas C. Zakas)
  • 86c5f37 docs: Update README (GitHub Actions Bot)
  • 19c0127 fix: improve message for no-console suggestions (#19483) (Francesco Trotta)
  • fbdeff0 docs: Update README (GitHub Actions Bot)
  • c9e8510 docs: generate deprecation notice in TSDoc comments from rule metadata (#19461) (Francesco Trotta)
  • 2f386ad docs: replace var with const in rule examples (#19469) (Tanuj Kanti)
  • 0e688e3 docs: Update README (GitHub Actions Bot)
  • 49e624f fix: improve error message for falsy parsed JS AST (#19458) (Josh Goldberg ✨)
  • 06b596d docs: Restore the carrot to the position where the search input was lost (#19459) (Amaresh S M)

v9.21.0 - February 21, 2025

  • a8c9a9f chore: update @eslint/eslintrc and @eslint/js (#19453) (Francesco Trotta)
  • 265e0cf chore: package.json update for @​eslint/js release (Jenkins)
  • 418717f feat: introduce new deprecated types for rules (#19238) (fnx)
  • 3401b85 test: add test for Rule.ReportDescriptor type (#19449) (Francesco Trotta)
  • e497aa7 chore: update rewrite dependencies (#19448) (Francesco Trotta)
  • c5561ea docs: Update README (GitHub Actions Bot)
  • db5340d fix: update missing plugin message template (#19445) (Milos Djermanovic)
  • d8ffdd4 fix: do not exit process on rule crash (#19436) (Francesco Trotta)
  • dab5478 chore: better error message for missing plugin in config (#19402) (Tanuj Kanti)
  • 80b0485 docs: replace var with let and const in rule example (#19434) (Tanuj Kanti)
  • ebfe2eb chore: set js language for bug report issue config block (#19439) (Josh Goldberg ✨)
  • f67d5e8 docs: Update README (GitHub Actions Bot)
  • 75afc61 docs: Update README (GitHub Actions Bot)
  • 5fd211d test: processors can return subpaths (#19425) (Milos Djermanovic)
  • 0636cab docs: Update Eleventy from v2 to v3 (#19415) (Amaresh S M)
  • 5c5b802 feat: Add --ext CLI option (#19405) (Milos Djermanovic)
  • dd7d930 docs: Update README (GitHub Actions Bot)

v9.20.1 - February 11, 2025

  • fe3ccb2 docs: allow typing in search box while dropdown is open (#19424) (Amaresh S M)
  • 274f054 fix: fix RuleContext type (#19417) (Francesco Trotta)
  • 93c78a5 docs: Add instructions for pnpm compat (#19422) (Nicholas C. Zakas)
  • b476a93 docs: Fix Keyboard Navigation for Search Results (#19416) (Amaresh S M)
  • ccb60c0 docs: Update README (GitHub Actions Bot)

v9.20.0 - February 7, 2025

  • 979097a chore: upgrade @​eslint/js@​9.20.0 (#19412) (Francesco Trotta)
  • 031734e chore: package.json update for @​eslint/js release (Jenkins)
  • 91d4d9f fix: Bring types in sync with @​eslint/core (#19157) (Nicholas C. Zakas)
  • b7012c8 docs: rewrite examples with var using let and const (#19407) (Mueez Javaid Hashmi)
  • d4c47c3 test: avoid empty config warning in test output (#19408) (Milos Djermanovic)

... (truncated)

Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Mar 10, 2025
Copy link

coderabbitai bot commented Mar 10, 2025

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (1)
  • build(

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.


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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

socket-security bot commented Mar 10, 2025

@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/eslint-9.22.0 branch from 0b92eaa to 6ebe305 Compare March 10, 2025 19:36
Bumps [eslint](https://github.com/eslint/eslint) from 8.57.1 to 9.22.0.
- [Release notes](https://github.com/eslint/eslint/releases)
- [Changelog](https://github.com/eslint/eslint/blob/main/CHANGELOG.md)
- [Commits](eslint/eslint@v8.57.1...v9.22.0)

---
updated-dependencies:
- dependency-name: eslint
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/eslint-9.22.0 branch from 6ebe305 to 2b39dc6 Compare March 10, 2025 19:42
@ckeshava
Copy link
Collaborator

I'd like to hear the opinions of other members regarding the choice of style-guide.

  1. The currently used airbnb style guide does not yet support ESLint v9. I'm not aware of their timelines for this migration. This issue is discussed here
  2. Google's javascript style guide has some inconsistencies with the valid-jsdoc rule. Consequently, we cannot use it as-is. Reference link. Although there is a fix for this issue, it has not been released into the latest release.

We have three choices -- Define all the rules ourselves manually, use the "recommended" ESLint rulesets (or) indefinitely delay this upgrade to ESLint v9.

I have implemented the second option for two packages in this PR. However, it comes with significant linter-upgrades across the packages. I have not fixed these linter warnings and errors.

Before we invest any more effort in this direction, I'd like to hear the opinions of other developers.

@ckeshava
Copy link
Collaborator

My thoughts regarding the previous msg:

Alternative-1: Using the ESLint:recommended setting is the best way forward. At the moment, we depend on the airbnb javascript style guide. Both airbnb and google-'s javascript style guide are not maintained frequently. We can sever our dependencies on external style guides.

Cons: This need developer time (I expect 1 week for 2 engineers). We need to migrate the codebase toward the new linter rules.

Alternative-2: At the same time, linters are not critical functionality. xrpl.js software will work correctly, even if we don't use the latest linters. We can afford to wait for a few more years (!?) to upgrade the linter.

Cons: This PR is already 10 files in diff. A future migration will need a lot more developer effort. We will effectively be kicking the ball down the road.

@khancode
Copy link
Collaborator

I'd like to hear the opinions of other members regarding the choice of style-guide.

  1. The currently used airbnb style guide does not yet support ESLint v9. I'm not aware of their timelines for this migration. This issue is discussed here
  2. Google's javascript style guide has some inconsistencies with the valid-jsdoc rule. Consequently, we cannot use it as-is. Reference link. Although there is a fix for this issue, it has not been released into the latest release.

We have three choices -- Define all the rules ourselves manually, use the "recommended" ESLint rulesets (or) indefinitely delay this upgrade to ESLint v9.

I have implemented the second option for two packages in this PR. However, it comes with significant linter-upgrades across the packages. I have not fixed these linter warnings and errors.

Before we invest any more effort in this direction, I'd like to hear the opinions of other developers.

@ckeshava ESLint v9 doesn’t bring any major functional improvements—its biggest change is the shift to the flat config system, which mainly affects configuration structure rather than linting capabilities. It's better to keep using ESlint v8 and indefinitely delay this upgrade.

@ckeshava
Copy link
Collaborator

@khancode I'm fine with that choice.

I'd like to invite @achowdhry-ripple 's thoughts here. He had remarked that the upgrade of the VHS code base was hinging on an upgrade of this javascript style guide. @achowdhry-ripple -- Would you be able to upgrade VHS to Node v18 without these changes?

Copy link
Contributor Author

dependabot bot commented on behalf of github Mar 24, 2025

A newer version of eslint exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants