We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
.ts
.js
Modern NodeNext resolve strategies, and Typescript team itself historically, require that imports end with .js extension.
NodeNext
The plugin right now simply appends extensions to try, rather than changing extensions. So if you have a TS project and have an import of the form:
import { Foo } from './foo.js';
The file to resolve may actually be called foo.ts on disk, and hence the current plugin resolve strategy won't find it.
foo.ts
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Modern
NodeNext
resolve strategies, and Typescript team itself historically, require that imports end with.js
extension.The plugin right now simply appends extensions to try, rather than changing extensions. So if you have a TS project and have an import of the form:
The file to resolve may actually be called
foo.ts
on disk, and hence the current plugin resolve strategy won't find it.The text was updated successfully, but these errors were encountered: