Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Please replace TSlint with ESlint #209

Closed
felipesilvati opened this issue Jul 14, 2019 · 2 comments
Closed

Please replace TSlint with ESlint #209

felipesilvati opened this issue Jul 14, 2019 · 2 comments

Comments

@felipesilvati
Copy link

According to palantir/tslint#4534, TSlint will be deprecated in the near future and it will be replaced with ESlint as the 'standard JavaScript and TypeScript' linter.

Please update the boiler-plate accordingly. Thank you.

@peterblazejewicz
Copy link
Collaborator

@felipesilvati
This could be a long road, but let's try. I've created the #211, so if you could, please look into proposed change and post your feedback.
Thanks!

peterblazejewicz added a commit that referenced this issue Jul 16, 2019
✨ Migrate TSLint to ESLint. Closes #209
@peterblazejewicz
Copy link
Collaborator

@felipesilvati Landed in the master. Current version should be polished out in near future.

brittanydrandolph pushed a commit that referenced this issue Jun 17, 2022
This commit rewrites linting support in the project to be based solely
on the ESLint as advised by the TSLint tool authors:
https://medium.com/palantir/tslint-in-2019-1a144c2317a9

The migration is based on default, recommended settings for TypeScript
in ESLint and is expected to be updated in future to better fit project
goals.

All references has been updated and replaced with relevant ESLint
context:

- dependencies migration from TSLint to ESLint
- VSCode configuration changes to support ESLint exension
- VSCode extensions recommendation changes
- `.eslintrc` and `.eslintignore` configuration files added
- all error level problems in the source files are covered by this
  migration

Thanks!
brittanydrandolph pushed a commit that referenced this issue Jun 17, 2022
✨ Migrate TSLint to ESLint. Closes #209
pull bot pushed a commit to nemoipaha/TypeScript-Node-Starter that referenced this issue Jul 2, 2022
This commit rewrites linting support in the project to be based solely
on the ESLint as advised by the TSLint tool authors:
https://medium.com/palantir/tslint-in-2019-1a144c2317a9

The migration is based on default, recommended settings for TypeScript
in ESLint and is expected to be updated in future to better fit project
goals.

All references has been updated and replaced with relevant ESLint
context:

- dependencies migration from TSLint to ESLint
- VSCode configuration changes to support ESLint exension
- VSCode extensions recommendation changes
- `.eslintrc` and `.eslintignore` configuration files added
- all error level problems in the source files are covered by this
  migration

Thanks!
pull bot pushed a commit to nemoipaha/TypeScript-Node-Starter that referenced this issue Jul 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants