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

Improve Deno compatibility between v1 and v2 #855

Open
wellwelwel opened this issue Nov 14, 2024 · 0 comments
Open

Improve Deno compatibility between v1 and v2 #855

wellwelwel opened this issue Nov 14, 2024 · 0 comments

Comments

@wellwelwel
Copy link
Owner

wellwelwel commented Nov 14, 2024

After the latest canary version (de34c7ed29bcce8b46a65f5effe45090b8493ba5), Deno requires the use of commonjs explicitly in the package.json for CommonJS interoperability.

Also, Deno v2 doesn't require the polyfill for CommonJS when using extensions as .cjs or setting "type": "commonjs" in the package.json.

It would be a good improvement to parse the Deno version after the mentioned canary release to enable users to continue using both the versions 1 and 2 in their workflows and environments.

  • After the mentioned canary version, only one of them is possible, requiring two workflows:
deno run npm:poku --denoCjs # Deno v1
deno run npm:poku           # Deno v2

Related

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant