fix: import removed from export map - #585

tools that don't yet recognize module-sync (confirmed: @rollup/plugin-commonjs

Is there an issue link?

So far I've opened a Nitro issue with a very minimal reproduction using meriyah:

• Nested dependency silently missing when its exports map has no import condition nitrojs/nitro#4456

I haven't reported to Rollup because it might be related to how they use the plugin.

Thanks, let's see how they repond first.

I've narrowed this down to two seperate bugs, one with @vercel/nft and another with nitropack.

Here is the other:

• Traced externals: module-sync export target pruned from .output/server/node_modules when building on Node 20 nitrojs/nitro#4468

This last one can be worked around via a moduleSyncCatchall setting which just tells nft to include all conditions.

@fisker any downside if we add import? I don't mind it if it helps for bypassing bugs from other tools.

any downside if we add import?

There shouldn't be.

This would give me great reason to push to upgrade to v7 and drop Node v18 support 🎉

Node 18 was already dropped.

Open in StackBlitz

npm i https://pkg.pr.new/meriyah@585

commit: 7a719ce

v7.2.0 is released.