An import path cannot end with a '.ts' extension.
See original GitHub issueFound deno, version:
deno: 1.1.0
v8: 8.4.300
typescript: 3.9.2
.vscode/settings.json
{
"deno.enable": true
}
Plugin: 1.25.0 VSCode: 1.46.0 OS: macOS 10.15.4
The plugin doesn’t seem to be working in any case. Reinstalled plugin, restarted VSCode, restarted TSServer, but still couldn’t get it working.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:7 (3 by maintainers)
Top Results From Across the Web
An import path cannot end with '.ts' - NodeJS and Visual Code
Even that Visual Code prompts an error, my code got running.. When I remove the .ts extension from import statement, I got an...
Read more >Suppressing "The import path cannot end with a '.ts' extension ...
So the output a.js will contain the same import specifier "./b.ts", although possibly translated to require("./b.ts") ...
Read more >An import path cannot end with a '.ts' extension. : r/Deno - Reddit
An import path cannot end with a '.ts' extension. · Install the Deno CLI. · Install this extension. · Ensure deno is available...
Read more >An import path cannot end with a '.ts' extension ... - Issuehunt
An import path cannot end with a '.ts ' extension. Consider importing 'xx.js' instead. #2750. cn3lfs posted onGitHub. <!-- Check those before opening...
Read more >Luca Casonato 🏳️ в Twitter: „My grand plan for 2022 1 ...
Add TSC config option to disable "An import path cannot end with a '.ts' extension. Consider importing './x.js' instead. ts(2691)" diagnostic 3.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Other plugins can cause this issue. I discovered that using “Disable (Workspace)” on the Volar plugin for Vue fixed the issue for me.
Same issue
Version: 1.48.1 (user setup) Commit: 3dd905126b34dcd4de81fa624eb3a8cbe7485f13 Date: 2020-08-19T17:12:13.244Z Electron: 7.3.2 Chrome: 78.0.3904.130 Node.js: 12.8.1 V8: 7.8.279.23-electron.0 OS: Windows_NT x64 10.0.18362
deno plugin: 2.0.13
deno: 1.2.2
typescript: 3.9.7
Add .vscode/settings.json and config
it worked.