Upgrade eslint to version 8.3.0 #90
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 upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint (^7.0.0 → ^8.3.0) · Repo · Changelog
Release Notes
8.3.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 41 commits:
8.3.0Build: changelog update for 8.3.0feat: add `allowProperties` option to require-atomic-updates (#15238)feat: update no-use-before-define for class static blocks (#15312)fix: update vars-on-top for class static blocks (#15306)fix: update semi-style for class static blocks (#15309)feat: update no-redeclare for class static blocks (#15313)feat: update no-inner-declarations for class static blocks (#15290)feat: support for private-in syntax (fixes #14811) (#15060)feat: Update espree and eslint-scope (#15338)feat: update max-depth for class static blocks (#15316)feat: update padded-blocks for class static blocks (#15333)feat: update the complexity rule for class static blocks (#15328)feat: update the indent rule for class static blocks (#15324)feat: update lines-around-comment for class static blocks (#15323)feat: update brace-style for class static blocks (#15322)feat: update max-statements for class static blocks (#15315)feat: update prefer-const for class static blocks (#15325)feat: code path analysis for class static blocks (#15282)feat: update eslint-scope for class static blocks (#15321)feat: update one-var for class static blocks (#15317)feat: update padding-line-between-statements for class static blocks (#15318)docs: Expand `--debug` option description in the CLI documentation (#15308)docs: the strict rule does not apply to class static blocks (#15314)Sponsors: Sync README with websiteSponsors: Sync README with websitefix: update no-invalid-this and no-eval for class static blocks (#15300)feat: update class-methods-use-this for class static blocks (#15298)feat: update no-lone-blocks for class static blocks (#15295)feat: update block-spacing for class static blocks (#15297)feat: update keyword-spacing for class static blocks (#15289)feat: update no-extra-semi for class static blocks (#15287)feat: update semi rule for class static blocks (#15286)Sponsors: Sync README with websitefeat: add examples for block-scoped-var with class static blocks (#15302)docs: Remove inconsistent colon in pull request docs (#15303)docs: remove deprecation note from lines-around-comment (#15293)docs: no-unused-expressions - class static blocks don't have directives (#15283)chore: upgrade eslint-visitor-keys for class static blocks (#15277)docs: Add variables option to no-use-before-define (#15276)feat: Normalize ecmaVersion to eslint-scope when using custom parser (#15268)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