extensions rule autofix "fixes" imports to files that don't actually exist

[hackel]

I'm running with

'import-x/extensions': ['error', 'ignorePackages', { fix: true }],

I have many index imports to files like e.g. /api/index.js which are currently imported as import '@/api'. When I run the fixer, it changes them to import '@/api.js' instead of @/api/index.js which causes my app to blow-up. I don't know if the fixer is attempting to actually resolve the files or not, and maybe this is outside the scope of this rule, but I don't think it should be auto-fixing at all if it can't be certain that it is a correct fix.

Thanks!

[magnusjtvisma]

I have the same problem.

My tsconfig file has settings that allow me to import actual typescript files with the .ts extension.

 "allowImportingTsExtensions": true,
 "rewriteRelativeImportExtensions": true

However, the ecosystem hasn't caught up with this yet, and for example my IDE assumes I want to import esm with .js instead. When I then run the import-x/extensions autofix it changes files to file.js.ts instead of file.ts.

[mikecentola]

I have the same problem.

My tsconfig file has settings that allow me to import actual typescript files with the .ts extension.

"allowImportingTsExtensions": true,
"rewriteRelativeImportExtensions": true
However, the ecosystem hasn't caught up with this yet, and for example my IDE assumes I want to import esm with .js instead. When I then run the import-x/extensions autofix it changes files to file.js.ts instead of file.ts.

@magnusjtvisma I'm not sure if this is the same issue but I think I have it working for me.

I have in my tsconfig as well:

 "allowImportingTsExtensions": true,
 "rewriteRelativeImportExtensions": true

My import-x config:

'import-x/extensions': [
                'error',
                'ignorePackages',
                {
                    'fix': true,
                },
            ],

And it seems to be working in my mocha config for importing some modules:

import { Ajv2020 } from 'ajv/dist/2020.js';
import { expect } from 'chai';
import { cncCodesJSONSchema } from '../src/index.ts';
import gsample from './sample/g-sample.json' with { type: 'json' };

eslint isn't showing any errors and it is not asking me to fix it. I suspect it is because it is a package and I have ignorePackages on.

If I try to import something from say my dist folder which is definitely js extension, then it tells me that it is missing the .ts and tries to add it.

I think the plugin needs to resolve the file before determining which type of extension it needs. I would imagine hat would help people converting packages to ESM.