[js] Upgrade @typescript-eslint/parser: 3.10.1 → 4.0.1 (major) #209
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?
✳️ @typescript-eslint/parser (3.10.1 → 4.0.1) · Repo · Changelog
Release Notes
4.0.1
4.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
chore: publish v4.0.1
fix(eslint-plugin): update parser dependency range (#2445)
chore: remove v4 prerelease script from actions
chore: publish v4.0.0
chore: regen yarn.lock and fix lint issues
chore: add downlevel-dts to all packages with type declarations
chore: update dependencies
fix(scope-manager): correct analysis of abstract class properties (#2420)
feat(typescript-estree): switch to globby (#2418)
feat(eslint-plugin): [no-unnecessary-condition][strict-boolean-expressions] add option to make the rules error on files without `strictNullChecks` turned on (#2345)
feat(eslint-plugin): add `consistent-type-imports` rule (#2367)
fix(typescript-estree): correct ChainExpression interaction with parentheses and non-nulls (#2380)
fix: correct decorator traversal for AssignmentPattern (#2375)
fix(eslint-plugin): [no-shadow] fix false-positive on enum declaration (#2374)
feat(eslint-plugin): [typedef] remove all defaults (#2352)
feat(eslint-plugin): [ban-ts-comment] change default for `ts-expect-error` to `allow-with-description` (#2351)
fix(eslint-plugin): [no-unused-vars] handle TSCallSignature (#2336)
feat: consume new scope analysis package (#2039)
feat: support ESTree optional chaining representation (#2308)
chore: setup automatic RC release for v4 branch
docs: adjust prettier snippet (#2427)
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