-
Notifications
You must be signed in to change notification settings - Fork 71
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
jco exports uses invalid alias based on WIT world package name #292
Comments
The workaround is to not use export interfaces, but it's probably better to just remove the invalid alias? |
The problem is that TypeScript doesn't support the above. We have a flag for supporting this via |
No Typescript was involved at all in this process. The export was definitely not in "quotes" in my code, I wonder if Rollup removed it during the bundling process? I will try the flag and see what happens, thank you |
Tried the flag and it works nicely thank you Guy. You were right, I'll close and shift this to Rollup |
Thanks for following up on the Rollup issue here! |
This issue has been resolved via rollup/rollup#5298 as part of [email protected]. |
|
Hi, it's me again
Given the following WIT that exports an interface named
reactivity
:the resulting ES module code is invalid because the world package name is also used:
The
:
is invalid JS syntax unfortunatelyThe text was updated successfully, but these errors were encountered: