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
I'm using deno and it requires explicit .ts extensions when importing files locally.
So for example this will not work: import { type PortKeyConfig } from "./../types/schemas";
import { type PortKeyConfig } from "./../types/schemas";
Instead it must be: import { type PortKeyConfig } from "./../types/schemas.ts";
import { type PortKeyConfig } from "./../types/schemas.ts";
Using node with ECMAScript also requires .js to be added, so I think it's a valuable option either way.
Could you help to add a config value where I can force the file extension to be added? e.g. appendFileExtension: '.ts' or something like that?
appendFileExtension: '.ts'
The text was updated successfully, but these errors were encountered:
Hello, Thanks for reporting, I believe this is a duplicate of #259, right?
Feel free to open a PR if you have some time to help the library strive! 🙏
Sorry, something went wrong.
Oh yes it is a duplicate and funnily enough we have the same workaround ;)
No branches or pull requests
I'm using deno and it requires explicit .ts extensions when importing files locally.
So for example this will not work:
import { type PortKeyConfig } from "./../types/schemas";
Instead it must be:
import { type PortKeyConfig } from "./../types/schemas.ts";
Using node with ECMAScript also requires .js to be added, so I think it's a valuable option either way.
Could you help to add a config value where I can force the file extension to be added? e.g.
appendFileExtension: '.ts'
or something like that?The text was updated successfully, but these errors were encountered: