TypeScript complains about file extensions in import statements

[marvinhagemeister]

Currently TypeScript complains about adding an .ts, .tsx, .js or .jsx extension to the import path.

Not sure what we can do on our end here.

Relevant TS issues:

• Suppressing "The import path cannot end with a '.ts' extension" error? microsoft/TypeScript#27481
• allow voluntary .ts suffix for import paths microsoft/TypeScript#37582
• Add support for URI style import microsoft/TypeScript#35749
• Provide a way to add the '.js' file extension to the end of module specifiers microsoft/TypeScript#16577

[developit]

Yeah, I'm at a bit of a loss here too :(

One option would be to allow extension-less imports, but that kinda breaks the "it's just modules" philosophy just to make TS happy.

[marvinhagemeister]

Just noticed: By default vscode will insert auto-imports for every function/value/class you use from another file and those are always without an extension.

EDIT: And having extensions in the file paths breaks cmd/control click to jump to the function definition

[developit]

@marvinhagemeister I'm not sure if its my config, but for me the imports are inserted with a file extension - but only if any current imports already have the extension.

[marvinhagemeister]

@developit Very strange, just to confirm: Does this happen inside a TS file with a .ts/.tsx import? Importing JS files with an extension is perfectly valid TS. They only have that weird exception for .ts/.tsx files.

[developit]

I think now you can choose to use .js extensions or no extensions for TS files, so this one can be closed out now (lmk if I've missed something).