This plugin adds TypeScript support to eslint-plugin-import
.
This means you can:
import
/require
files with extension.cts
/.mts
/.ts
/.tsx
!- Use
paths
defined intsconfig.json
. - Prefer resolve
@types/*
definitions over plain.js
. - Multiple tsconfigs support just like normal.
exports
fields support inpackage.json
After version 2.0.0, .d.ts
will take higher priority then normal .js
files on resolving node_modules
packages in favor of @types/*
definitions.
If you're facing some problems on rules import/default
or import/named
from eslint-plugin-import, do not post any issue here, because they are just working exactly as expected on our sides, take import-js/eslint-plugin-import#1525 as reference or post a new issue to eslint-plugin-import instead.
# npm
npm i -D eslint-plugin-import eslint-import-resolver-typescript
# pnpm
pnpm i -D eslint-plugin-import eslint-import-resolver-typescript
# yarn
yarn add -D eslint-plugin-import eslint-import-resolver-typescript
Add the following to your .eslintrc
config:
- Make sure your change is covered by a test import.
- Make sure that
yarn test
passes without a failure. - Make sure that
yarn lint
passes without conflicts. - Make sure your code changes match our type-coverage settings:
yarn type-coverage
.
We have GitHub Actions which will run the above commands on your PRs.
If either fails, we won't be able to merge your PR until it's fixed.
Detailed changes for each release are documented in CHANGELOG.md.