How do I add custom conditions to the email commands?

[genzzo]

I have a package with custom export conditions, which I need to set for the emails to work properly.

In node, I can just do node --conditions=email index.js. But since react-email has their own bundler it does not seem to work the same way.

[apoorva-01]

Short version: you can't pass it, and --conditions wouldn't reach it anyway.

react-email doesn't use Node's resolver to load your templates. It runs its own esbuild build() internally (see get-email-component.ts), and node --conditions=email only affects Node's module resolution, not esbuild's bundling. So the flag just gets ignored.

The other half of the problem is that the esbuild options are hardcoded and not exposed, so there's no conditions array you can set through the CLI either. It bundles with roughly:

build({ bundle: true, platform: 'node', format: 'esm', jsx: 'automatic', ... })

With platform: 'node' + format: 'esm', esbuild resolves the standard conditions: import, module, node, default. Your custom email condition isn't in that set and there's no hook to add it.

Two ways around it:

• Make the target reachable under a condition esbuild already uses. In that package's exports, put the email build under "default" (or "node"/"import") as the fallback, so esbuild resolves it without needing the email key.
• Or skip conditions entirely and import the concrete subpath/file directly in your email template.

If you genuinely need custom conditions honored, that's a feature request on react-email to forward esbuild config (or expose a conditions option). Worth opening one if it isn't already tracked.