You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My understanding is that this means everything with the .ts extension in the import is run through the typescript transpiler plugin.
However, Typescript 2.0.3 (called externally for intellisense) will report this as an error: An import path cannot end with a ".ts" extension. Consider importing './app.routing' instead, for instance. Of course, if I do that, the .ts files aren't transpiled by systemjs, and it just reports 404's as it tries to load "./app.routing" which doesn't exist.
Is there a work-around so I don't have to choose between SystemJS and my intellisense?
Apologies if this is the wrong place to raise this issue.
0.17.0-beta.28
Running against local jspm install.
The text was updated successfully, but these errors were encountered:
Generating a new project with jspm init and specifying typescript as my transpiler, the convention for picking up typescript files is as follows:
My understanding is that this means everything with the .ts extension in the import is run through the typescript transpiler plugin.
However, Typescript 2.0.3 (called externally for intellisense) will report this as an error:
An import path cannot end with a ".ts" extension. Consider importing './app.routing' instead
, for instance. Of course, if I do that, the .ts files aren't transpiled by systemjs, and it just reports 404's as it tries to load "./app.routing" which doesn't exist.Is there a work-around so I don't have to choose between SystemJS and my intellisense?
Apologies if this is the wrong place to raise this issue.
The text was updated successfully, but these errors were encountered: