Bump @typescript-eslint/parser from 4.33.0 to 5.0.0

[dependabot]

Bumps @typescript-eslint/parser from 4.33.0 to 5.0.0.

Release notes

Sourced from @​typescript-eslint/parser's releases.

v5.0.0

5.0.0 (2021-10-11)

Breaking Release Notes

All Packages

• Support for ESLint v8 (see individual packages for relevant breaking changes).
• Drop support for Node v10 - required node version is now ^12.22.0 || ^14.17.0 || >=16.0.0.
  • Node v10 was EOL'd in April 2021, and ESLint v8 dropped support for it too.
• Drop Support for ESLint v5
  • ESLint v5 is now 3 years old - why are you still using it? Upgrade to at least ESLint v6.

ESLint-Plugin

• Changes to the recommended rule set - see #3746
• [ban-types] remove object from the default ban list
  • This has been a point of contention for a while - I originally added it because TS currently makes it impossible to narrow the type nicely. However there ultimately isn't a good alternative to this type for many usecases. As such we're removing the default ban. If you want to continue banning it, you can configure the rule to do so.
• [comma-dangle] align schema with ESLint v8
  • Should be pretty transparent unless you were using an invalid config.
• [explicit-member-accessibility] now checks abstract members
• [member-ordering] add support for getters and setters
  • This will likely cause your codebase's sort orders to change if you're using the default config.
• [no-unused-vars-experimental] rule has been deleted
  • You should instead use @typescript-eslint/no-unused-vars instead! It has had full and awesome support for TypeScript since v4.9.0 - and it doesn't require type information!

Experimental-Utils:

• Remove SourceCode#getComments API from ESLint types.
  • This API was deprecated in ESLint v4, and its usage will error in ESLint v8.
• Support ESLint v8:
  • CLIEngine is now conditionally undefined. It was deprecated in v7 and removed in v8. If you're still using it, you should upgrade to the ESLint API.
  • Remove meta.docs.category. ESLint has removed this from their core rules as it wasn't ever very useful and was always poorly done. We have followed suit and removed it from our types and our rules.

TypeScript-ESTree / AST-Spec

• Change .source of ExportNamedDeclaration, ExportAllDeclaration and ImportDeclaration to StringLiteral and add parse-time errors.
  • This ensures we're aligned with ESTree and producing the correct AST.
• Remove TSParenthesizedType node.
  • This node was added when this project was first created because the TS-AST includes this node. However it ultimately conveys no actual AST meaning (just like parentheses in non-type code). Babel removed this node earlier this year.
  • We expect rules will continue to "just work". In a lot of cases rules will work better as they no longer need manual checks to "look past" the useless node.
• Remove legacy option useJSXTextNode.
  • This option was added for compatibility between different ASTs a very long time ago - but all ASTs have converged on using JSXText - so you should be using that too.
• Align class features AST with ESTree. This aligns with ESLint v8.
  • ClassProperty is now called PropertyDefinition
  • TSAbstractClassProperty is now called TSAbstractPropertyDefinition
• TSAbstractPropertyDefinition.value is now always null.
  • It never made sense that this was allowed, and TS4.4 has now made this invalid.
• Add full support for PrivateIdentifier (#private class members)
  • Previously we did not officially support them and emitted an "unstable" AST.

... (truncated)

Changelog

Sourced from @​typescript-eslint/parser's changelog.

5.0.0 (2021-10-11)

Features

• support ESLint v8 (#3737) (4ca62ae)

Commits

• 101abc7 chore: publish v5.0.0
• c304a55 chore: bump eslint to 8.0.0
• 3ed09bd chore(eslint-plugin): remove support for eslint 5 (#2683)
• 4ca62ae feat: support ESLint v8 (#3737)
• b63013a chore: bump Node to ESLint 8.0 ranges (#3767)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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)