Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Introduce Biome for lint instead of TSLint #877

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

unvalley
Copy link

@unvalley unvalley commented Nov 11, 2023

Closes #168
This PR introduces Biome instead of TSLint. I enabled only lint feature. I skip formatter and analyzer here.

This PR was created because of its superiority over ESLint in terms of speed, readiness to install formatter features.
ESLint and typescript-eslint have the advantage of being de facto with abundant rules. If ESLint is needed, I will close this PR and create a PR that uses that one.

Referencing previous tslint.json, TSLint rule triple-equals is enabled by default in Biome as noDoubleEquals.
Others are set false, so ignored (it means, there is no need to suppress Biome's lint rules if the lint command passes).

Caring about disabled TSLint rules in comments (I deleted):

  • max-line-length is responsibility of the formatter in Biome.
  • no-shadowed-variable is not implemented in Biome, but discussed here.

NOTICE

Currently, Biome cannot handle lint rules that require TypeScript type info. For example, no-floating-promise. The team would like to address this, but has not found a definitive solution.
So, in this TSLint's recommended set, biome can't handle the lint rules require type info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migrate TSLint to ESLint
1 participant