fix: Include 'module' import condition in resolve.conditions

[justinvdm]

Change

Adds module import specifier to the resolve.conditions for all three environments (ssr, worker, client).

Context

ShadCN users were running into this issue:

TypeError: Cannot destructure property '__extends' of 'import_tslib.default' as it is undefined.

This appears to happen because:

• tslib has various import specifiers, including
  • one that maps node import specifier to a wrapper that module that imports its cjs build, and reexports it as an esm via a default export (code)
  • one that maps module import specifier to an esm module (code)
  • Since fix: Support packages with only node import condition and no workerd condition #510, we added a node import condition to the worker and ssr import conditions, meaning it would resolve to tslibs esm wrapper around its cjs build
  • This would be fine, except esbuild adds a wrapper to convert the cjs build to an esm build
  • Since tslib's own esm wrapper imports the default import for the cjs build, it doesn't get the named exports created by esbuild's wrapper

Links

• Discussion: https://discord.com/channels/679514959968993311/1383029083272646667/1383033401128255528
• Wrong exports in tslib microsoft/tslib#161