update to ts-eslint 7.x, eslint-plugin-import #1440
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://typescript-eslint.io/blog/announcing-typescript-eslint-v7/
https://typescript-eslint.io/blog/announcing-typescript-eslint-v6/#rule-breaking-changes
A big change upgrading from v5 is that import lints were dropped from
@typescript-eslint/
6.x and newer in favor of the official eslint plugin.Disabling a few recommended lints in this PR, but a followup PR with code changes can turn them on again.
Real problems found:
import/export
parserOptions.project
was left undefined, so while tsconfig.json files were being used in the build, they were never seen by eslint at all.The test files needed their own, separate tsconfig.json added. Without one, it complains if you run this:
xchainjs-lib/packages/xchain-bitcoin/package.json
Line 32 in b5b6bba
(And you can't add test files to the workspace's tsconfig.json, because it changes the inferred value for
rootDir
fromsrc/
to./
, which changes typescript's build output fromlib/index.d.ts
tolib/src/index.d.ts
.)