package.json: conditional exports: deno export

[balupton]

I couldn't find any documentation about this on:

• https://deno.com/blog/v1.31#packagejson-support
• https://deno.land/[email protected]/node/package_json

Node.js now supports a feature called conditional exports:

• https://nodejs.org/api/packages.html#conditional-exports

Would be cool if there was support for a deno export, such that I could write code that specifically has a different export for Node node, Deno deno, Browsers import, and legacy Node require/default

For instance, my start-of-week package writes different code for each target, so it would definitely use this. Currently it is using boundation with editions to achieve the conditional loading, however now that Node.js has its own official convention, I am planning to adopt that instead for all my packages.

[balupton]

I did find this however:

• https://runtime-keys.proposal.wintercg.org/#deno

Perhaps it is supported? but not documented anywhere officially?

[bartlomieju]

Yes, this has been supported for several releases already - you can use deno condition. I believe this was in the manual, but somehow dissappeared.

[kigawas]

It seems here: https://deno.land/x/[email protected]/node/compatibility_mode.md?source=#module-resolution

But it does not work on deno 2 (seemingly?)

[kigawas]

@bartlomieju @balupton

Alright I see. When there is a package A with exports deno condition, if we import A directly with deno, deno export works. If we import package B using package A, deno export will not work