Update @eslint/js 9.16.0 → 9.17.0 (minor) #654
Merged
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 upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @eslint/js (9.16.0 → 9.17.0) · Repo · Changelog
Release Notes
9.17.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 37 commits:
9.17.0
Build: changelog update for 9.17.0
chore: upgrade to `@eslint/[email protected]` (#19242)
chore: package.json update for @eslint/js release
feat: add suggestions to `no-unused-vars` (#18352)
chore: add missing backticks to `flags.js` (#19226)
docs: update `yoda` to `Yoda` in `yoda.md` for consistency (#19230)
docs: add missing backticks to `no-sequences` (#19233)
docs: Update README
docs: [no-await-in-loop] expand on benefits and inapplicability (#19211)
fix: fix crash when `message.fix` is nullish (#19168)
docs: add missing backticks to `func-style` (#19227)
chore: update dependency eslint-plugin-expect-type to ^0.6.0 (#19221)
chore: add type definitions for the `eslint-config-eslint` package (#19050)
docs: add missing header to `prefer-spread` (#19224)
docs: update description of `no-param-reassign` (#19220)
docs: add missing backticks to `prefer-destructuring` (#19223)
docs: add missing backticks to `no-unneeded-ternary` (#19222)
chore: fix incorrect `name` property in `integration-tutorial-code` (#19218)
docs: add missing backticks to `no-new-func` (#19219)
docs: add missing backticks to `id-length` (#19217)
fix: ignore vars with non-identifier references in no-useless-assignment (#19200)
docs: add missing backticks to `complexity.md` (#19214)
docs: add missing `)` to `id-denylist` (#19213)
docs: Update README
docs: add CSS language to `no-restricted-syntax` (#19208)
chore: Upgrade cross-spawn to 7.0.6 (#19185)
docs: add missing backticks to `eqeqeq` (#19207)
docs: add missing backticks to `prefer-object-spread` (#19206)
docs: update docs and `description` of `require-unicode-regexp` (#19205)
docs: Update README
docs: update comments and `description` of `no-script-url` (#19203)
docs: add missing backtick to `default-case-last` (#19202)
docs: add missing punctuation in document (#19161)
docs: replace quote with backtick in `description` of `for-direction` (#19199)
docs: use higher contrast color tokens for code comments (#19187)
docs: Update README
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