Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An import path cannot end with a ".ts" extension. (TS 2.0.3) #2103

Closed
jlost opened this issue Oct 2, 2016 · 1 comment
Closed

An import path cannot end with a ".ts" extension. (TS 2.0.3) #2103

jlost opened this issue Oct 2, 2016 · 1 comment

Comments

@jlost
Copy link

jlost commented Oct 2, 2016

Generating a new project with jspm init and specifying typescript as my transpiler, the convention for picking up typescript files is as follows:

packages: {
    "pets-gui": {
      "main": "main.js",
      "meta": {
        "*.ts": {
          "loader": "plugin-typescript"
        }
      }
    }
  }

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.
@guybedford
Copy link
Member

It would probably be best raising this with the plugin-typescript project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants