`extensions` should not ignore subpath imports when `ignorePackages` is used

[IanVS]

I have decided to add extensions to my typescript module imports, and import-x/extensions has been a godsend for the migration. However, one thing I've noticed is that when using the ignorePackages option, subpath imports like #api/... are treated as packages. I think you should be able to look for an import specifier starting with # (required by the node spec) and treat it as a subpath import, not a package.

[JounQin]

Yes, in next major.

eslint-plugin-import-x/src/utils/resolve.ts

Lines 331 to 336 in 27b175f

	// TODO: enable the following in the next major
	// {
	// ...resolverOptions,
	// extensions:
	// resolverOptions.extensions || settings['import-x/extensions'],
	// },

You can specify extensions option for resolver instead for now.

[IanVS]

Thank you, but I don't quite understand how this can help me.

I currently have imports written without extensions, like import { Link } from '#components/atoms/link/Link';, and a subpath import specified as:

    "#components/*": [
      "./src/components/*",
      "./src/components/*.ts",
      "./src/components/*.tsx",
      "./src/components/*/index.ts"
    ],

I want this plugin to automatically find and add the correct .ts or .tsx extensions to these files. What extensions option could I add to createTypeScriptImportResolver() which would continue to ignore imports from node_modules, but still enforce extensions on these subpath imports?