-
Notifications
You must be signed in to change notification settings - Fork 63
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
Deno compat/bypass for Jiti #168
Comments
Hi dear @birkskyum thanks for opening issue but i am wondering does deno has same Node.js compatibility surface of Bun? (does it support mixed ESM/CJS and importing other files without |
Good question. Actually, I believe it's more picky. It does support CJS modules, but if I understand the announcement made that is only if they are used inside dependencies imported through a |
Surely! We might also use a deno-specific ast transformer to handle necessary transformations (add extension, remap modules, etc) if that's what is needed on jiti side I'm totally up to it (only is a pitty because this way, Deno usage will be slower but i respect all reasons Deno runtime chose to keep stricter with ESM standards and disallow mixed syntaxes) @birkskyum while you are here, are you also in UnJS discord channel? If not and like to work closely, my handle is |
We have introduced new Also made bun option generic to |
Environment
Similar to bun here
It would be great to have a bypass for Deno.
Reproduction
Repro here
Describe the bug
Jiti should not try to compile typescript when using Deno
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: