Does tsc support importing for relative path with extension?

[unional]

Currently import myClass from './myClass.ts'; transpile to var myClass_ts_1 = require('./myClass.ts')'.

Since myClass.ts is transpile to myClass.js, the transpiled code does not work.

I try to stick to pure ES6 as much as possible so I want to avoid using internal module syntax.

Thanks!

[unional]

FYI doing jspm bundle to transpile the code works as it is transpiled to System.register('./myClass.ts', ...) therefore the referencing still work correctly.

[vladima]

out of curiosity, why do you need to specify an extension in import? import myClass from "./myClass" should also work

[unional]

Because that is the suggested convention for referencing the file name. As in:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import
https://hacks.mozilla.org/2015/08/es6-in-depth-modules/

excerpt:
module-name: The name of the module to import. This is a file name.

systemjs will also depreciate defaultJSExtension in the future.

I can't remember the exact reason.

[weswigham]

Duplicates #4595?

[unional]

Yes it is the same issue, but targeting compile/transpile logic in tsc instead of loading in application. The objective is to create a npm/jspm module that is transpiled.

I have a related issue on jspm that tries to see if a pure, raw typescript module is possible.

[mhegazy]

They both seem to be stemming form the same issue. we need to reach a solution, we have been waiting on the loader spec to solidify.