-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Closed
Labels
accepting prsGo ahead, send a pull request that resolves this issueGo ahead, send a pull request that resolves this issuebreaking changeThis change will require a new major version to be releasedThis change will require a new major version to be releasedgood first issueGood for newcomersGood for newcomersrepo maintenancethings to do with maintenance of the repo, and not with code/docsthings to do with maintenance of the repo, and not with code/docs
Description
Suggestion
Consider whether we should raise tsconfig target / lib from ES2017 to something higher.
typescript-eslint/tsconfig.base.json
Lines 16 to 17 in 91d71bc
"target": "es2017", | |
"lib": ["es2017"], |
We're already planning to increase requirements for v6 including:
- chore: drop support for ESLint v6 #5972 (released 2019)
- Drop support for NodeJS v12 #5917 (released 2019, EOL 2022)
- feat: bump minimum supported TS version to 4.2.4 #5915 (released Feb 2021)
This all seems to indicate people would have a relatively modern environment to run TypeScript linting in.
The newest possible we could use is ES2021
, is that too new or is there any reason we couldn't use that?
This may be a breaking change that could be included with v6 (#5886).
Metadata
Metadata
Assignees
Labels
accepting prsGo ahead, send a pull request that resolves this issueGo ahead, send a pull request that resolves this issuebreaking changeThis change will require a new major version to be releasedThis change will require a new major version to be releasedgood first issueGood for newcomersGood for newcomersrepo maintenancethings to do with maintenance of the repo, and not with code/docsthings to do with maintenance of the repo, and not with code/docs