You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the latest canary version (de34c7ed29bcce8b46a65f5effe45090b8493ba5), Deno requires the use of commonjs explicitly in the package.json for CommonJS interoperability.
Also, Denov2 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
After the latest canary version (
de34c7ed29bcce8b46a65f5effe45090b8493ba5
), Deno requires the use ofcommonjs
explicitly in the package.json forCommonJS
interoperability.Also, Deno
v2
doesn't require the polyfill forCommonJS
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
and2
in their workflows and environments.Related
v2
requirescommonjs
type explicitly sidorares/node-mysql2#3209The text was updated successfully, but these errors were encountered: