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

TypeScript Files Not Automatically Converted to ECMAScript Modules (.mjs) #350

Open
productdevbook opened this issue Dec 22, 2023 · 2 comments

Comments

@productdevbook
Copy link

When importing a TypeScript file using the .ts extension, the build process does not automatically convert it to an ECMAScript module with the .mjs extension. This leads to import errors, as the expected file format is not found.

await import(_resolver.resolve("./seed/index.ts"))

After import build there is a problem because .ts does not convert to mjs. How can I do this

await import(_resolver.resolve("./seed/index.mjs"))
@pi0
Copy link
Member

pi0 commented Jan 15, 2024

Can you please make a runnable reproduction so I can test? 🙏🏼

@angelhdzmultimedia
Copy link

Can you please make a runnable reproduction so I can test? 🙏🏼

I replied to this Issue but then deleted the reply to have a better understanding.

After so much playing around, I reached the conclusion that this Issue matches mine.

unbuild is failing to add the .mjs extension to the source code of the built files for dynamic imports without extension
await import("/path/to/module")
should convert to
await import("/path/to/module.mjs") so that it can be loaded with node at runtime. But then Node throws an error that the module is not found because of the missing extension. Adding the extension manually solves this apparently.

In my case I'm building a nuxi add/nuxi new inspired CLI to add more templates and using inquirer package to select templates and configurations, it's a binary/executable, so I don't know how to tell Node to use some loader that adds the extension. So my only option is after running unbuild, adding the .mjs everywhere I import dynamically.
Yes, I modified build.config.ts to pack the ~/src/templates and ~/src/utils directories and they are being generated and their .ts files converted to .mjs.

My drastic workaround was, instead of loading the templates .ts files at runtime, I imported them statically in the ~/src/templates/index.ts (the same way nuxi does), so now there's no issue with it. You can check it here: https://github.com/angelhdzmultimedia/ahdz-nuxt-scaffold.

Any info will be highly appreciated. 🔥💚🤝😊

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

3 participants