VS plugin marks import with extension as an error

[outring]

According to the #4595, file extensions are now allowed to be present in imports, but it's still highlighted as an error by IntelliSense.

TypeScript Version: 2.0.3.0

Code

import {foo} from "./bar.ts";
import {foo2} from "./bar2.tsx";

Expected behavior: No "An import path cannot end with a '.ts' extension" error

Actual behavior: "An import path cannot end with a '.ts' extension" error

[outring]

I've read #9538 and it seems that you disallowed it intentionally, but what's your proposition of using TS with system.js since they permitted omitting the extension, as stated in #4595? And especially when you need to distinguish *.ts and *.tsx, no defaultExtension option for system.js will help :(

[mhegazy]

According to the #4595, file extensions are now allowed to be present in imports, but it's still highlighted as an error by IntelliSense.

output file extensions are allowed. i.e. ./bar.js. One thing to note is that the compile will not change your module name. so if you write import ... from "./bar.js" the output will be require("./bar.js"). So since the .ts files do not exist at runtime, importing ./bar.ts is going to fail, and thus is flagged as an error.

[outring]

Hi, @mhegazy. When using system.js all compilation could work right in the browser, this is what plugin-typescript does. So you need to be able to load actual .ts/.tsx files. It's simplifies everything a lot: you don't need to precompile anything — it just works.
The same way work all other loader plugins for system.js, like css, sass and so on — you just need to be able to specify exact url for the file.

[outring]

I understand that it made to prevent some confusion. Since it's only the system.js (I guess) requirement/feature, so probably such behavior should be allowed when module format is set to system.js only

[mhegazy]

SystemJs has support for defaultExtension, is not that sufficient here?

[outring]

Even if it works, we still need to distinguish *.ts and *.tsx

[glebmachine]

Still got this error

[aluanhaddad]

@glebmachine why not use

packages: {
  "app": {
    "defaultExtension": "ts"
  }
}

If you have tsx and ts files in the same directory, you can either split them into different directories, setting different default extensions, or you can change the ts files to tsx files.

[asdacap]

I have the same issue with the VSC plugin. I'm using webpack with ts-loader, so (AFAIK) the extension is required because of the loader extension test. If I remove the extension, webpack crash with 'cannot find file' error, if I add the extension, VSC shows a red line and no intellisence for that module.

[aluanhaddad]

No it is not required. Stop using it.

[aluanhaddad]

systemjs+/- jspm with typescript

webpack with typescript via ts-loader
webpack with typescript via awesome-typescript-loader

[asdacap]

Sorry, my bad. Did not include the resolve.extensions configuration.