Open alex-r-bigelow opened 2 years ago
Unfortunately @blueprintjs/eslint-config
still uses a couple rules which we never migrated from TSLint to ESLint. For the most part these TSLint rules do not have ESLint equivalents with the same semantics. It's on the to-do list to eventually migrate over and release a new major version of @blueprintjs/eslint-config
which drops the tslint
dependency, but in the meantime, there's no harm in having tslint
as a dependency. It will run a few rules for you via @typescript-eslint/tslint
.
This issue will remain open until we migrate these remaining rules (no-submodule-imports and object-literal-sort-keys) to ESLint. I hope to do that sometime in the next few months.
Environment
Question
I'm attempting to upgrade the dependencies in a project (yes, blueprint itself is on the list), but I'm hitting an error that doesn't appear to be relevant to blueprint's v3 -> v4 migration, in that
@blueprintjs/eslint-config
is still importing the deprecatedtslint
package. Trying toyarn remove tslint
from my project results in this error:There are some un-configurable / outdated
tslint
rules that are currently a blocker for me; any guidance for using blueprint without including the outdatedtslint
package? Or would migrating v3 -> v4 first fix this problem?