Update @eslint/js 9.1.1 → 9.3.0 (minor) #393
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @eslint/js (9.1.1 → 9.3.0) · Repo · Changelog
Release Notes
9.3.0
9.2.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 43 commits:
9.3.0Build: changelog update for 9.3.0chore: update dependencies for v9.3.0 release (#18469)chore: package.json update for @eslint/js releasefix: Improve config error messages (#18457)docs: explain how to use "tsc waiting" label (#18466)feat: add `overrides.namedExports` to `func-style` rule (#18444)chore: update dependency @humanwhocodes/retry to ^0.3.0 (#18463)fix: don't remove comments between key and value in object-shorthand (#18442)docs: Add troubleshooting info for plugin compatibility (#18451)docs: Update READMEfix: object-shorthand loses type parameters when auto-fixing (#18438)feat: add `restrictedNamedExportsPattern` to `no-restricted-exports` (#18431)docs: Update READMEdocs: Clarify usage of `no-unreachable` with TypeScript (#18445)docs: Fix typos (#18443)feat: add option `allowEscape` to `no-misleading-character-class` rule (#18208)docs: Update READMEfeat: deprecate `multiline-comment-style` & `line-comment-position` (#18435)refactor: Use `node:` protocol for built-in Node.js modules (#18434)docs: update deprecation notice of `no-return-await` (#18433)docs: Link global ignores section in config object property list (#18430)fix: don't crash when `fs.readFile` returns promise from another realm (#18416)chore: update dependency markdownlint-cli to ^0.40.0 (#18425)chore: update actions/stale action to v9 (#18426)chore: update actions/upload-artifact action to v4 (#18427)chore: Disable documentation label (#18423)docs: reflect release of v9 in config migration guide (#18412)feat: add `enforceForInnerExpressions` option to `no-extra-boolean-cast` (#18222)docs: fix grammar in configuration file resolution (#18419)9.2.0Build: changelog update for 9.2.0chore: upgrade @eslint/[email protected] (#18413)chore: package.json update for @eslint/js releasechore: package.json update for eslint-config-eslint releasedocs: Update READMEchore: remove eslintrc export from eslint-config-eslint (#18400)feat: `no-case-declarations` add suggestions (#18388)feat: update Unicode letter detection in capitalized-comments rule (#18375)docs: update wording regarding indirect eval (#18394)ci: run tests in Node.js 22 (#18393)fix: do not throw when defining a global named __defineSetter__ (#18364)docs: update to eslint v9 in custom-rule-tutorial (#18383)Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands