Skip to content

docs: add import/no-unresolved to perf troubleshooting docs #8190

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.

Sign up for GitHub

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

Merged
merged 7 commits into from
Jan 28, 2024
Merged

docs: add import/no-unresolved to perf troubleshooting docs #8190

Changes from all commits
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
e77be94
docs: update Performance.mdx
Zamiell Jan 4, 2024
7aa1f47
Update Performance.mdx
Zamiell Jan 4, 2024
aaecc11
Update Performance.mdx
Zamiell Jan 4, 2024
88b7b8a
Update Performance.mdx
Zamiell Jan 11, 2024
09fe683
Update Performance.mdx
Zamiell Jan 11, 2024
6b8f1eb
Update Performance.mdx
Zamiell Jan 13, 2024
6bd2063
Update Performance.mdx
Zamiell Jan 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/linting/troubleshooting/Performance.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,7 @@ We recommend you do not use the following rules, as TypeScript provides the same
- `import/namespace`
- `import/default`
- `import/no-named-as-default-member`
- `import/no-unresolved` (as long as you are using [`import` over `require`](https://typescript-eslint.io/rules/no-var-requires/))

The following rules do not have equivalent checks in TypeScript, so we recommend that you only run them at CI/push time, to lessen the local performance burden.

Expand Down