`import/extensions` not flagging missing extension on TypeScript path imports about eslint-plugin-import

[nemanjastanic]

@nemanjastanic does it work if you use a different character?

yes, i got it to work, thanks btw!

[ljharb]

Extensions don't apply to things that aren't relative paths - @a/file is a package, and it wouldn't work if you appended an extension.

[nemanjastanic]

Extensions don't apply to things that aren't relative paths - @a/file is a package, and it wouldn't work if you appended an extension.

Like I mentioned, it is a TypeScript path, it's not a package.

Even so, why is there an option for ignorePackages as the second argument of the rule then?

[ljharb]

That’s not node, that’s up to the package - and a package that has chosen an extension for an entry point has failed at DX :-)

ignorePackages should be true for everyone, it’s just legacy that keeps the default what it is.

I strongly suggest not using @ for aliases, since that character is already used by npm scopes. What happens if you use a different character in the TS alias?

[ljharb]

@nemanjastanic does it work if you use a different character?