Docs: Mention import-no-unresolved as unnecessary in Performance Troubleshooting?

[JoshuaKGoldberg]

Before You File a Documentation Request Please Confirm You Have Done The Following...

• I have looked for existing open or closed documentation requests that match my proposal.
• I have read the FAQ and my problem is not listed.

Suggested Changes

Spinning out of https://stackoverflow.com/questions/77435417/how-to-resolve-module-federation-import-paths-in-eslint-with-typescript: https://typescript-eslint.io/linting/troubleshooting/performance-troubleshooting/#eslint-plugin-import does not mention import/no-unresolved. But it seems to me like import/no-unresolved is probably unnecessary when used with TypeScript, no? Perhaps we should add it to the list of avoidable rules?

Affected URL(s)

https://typescript-eslint.io/linting/troubleshooting/performance-troubleshooting

[bradzacher]

It can be useful for some webpack setups so you can enforce css files and other assets exist. But by and large its no good yeah and super expensive due to the disk lookups.

At Canva though I whipped together a rule targeting just imports with asset extensions and it saved SO MUCH TIME

[JoshuaKGoldberg]

Great - let's add it in, with that caveat. https://github.com/import-js/eslint-plugin-import/blob/6d34c88a91a9cb7556700b7cb83c8a27731ff302/docs/rules/no-unresolved.md#ignore looks like it can be used to ignore extension-less imports?

[bradzacher]

@JoshuaKGoldberg I don't think so? Regexes aren't good for "negative" matchers. EG I don't think you can craft a regex that says "match all imports without an extension". You can easily craft the opposite - but that doesn't work because it's an ignore option.

This is why naming-convention defined its regex config with a boolean to invert the regex result.

[Josh-Cena]

EG I don't think you can craft a regex that says "match all imports without an extension"

You can definitely do that! 😄 /$(?<![^\s.]\.[^\s.]+)/

[bradzacher]

Yeah but negative lookaheads are disgusting to use for this exact purpose

[JoshuaKGoldberg]

#8926 is reworking the FAQs a bit. Marking as blocked in the meantime.

[JoshuaKGoldberg]

Ah, #8507 added a line:

typescript-eslint/docs/troubleshooting/typed-linting/Performance.mdx

Line 123 in 635133a

- `import/no-unresolved` (as long as you are using [`import` over `require`](/rules/no-var-requires/))

So this was done. ✅