Subpath exports for individual components (react-email/components/*)

[mattwigham]

Goals

1. Let browser-side consumers import a single component without pulling in marked / prismjs / tailwindcss from the consolidated dist.
2. Replace the deprecated individual @react-email/* packages with a first-class narrow-import path that still lives under the react-email umbrella.

Background

We render a few React Email components client-side inside a live email editor (built on @react-email/editor). Migrating from the now-deprecated individual @react-email/* packages to react-email v6 adds +190 KB gzip (+33%) to our editor chunk — measured on a Vite/rolldown build.

Tree-shaking can’t recover it: the consolidated dist/index.mjs has top-level imports of prismjs / marked / tailwindcss plus a top-level Prism$1.languages.markup = {...} side effect, so even import { Body } from "react-email" keeps all three heavy deps. Patching sideEffects: false would drop the Prism registration too, so that’s not safe.

Current alternatives aren't great: keep the deprecated packages (forever install warnings), alias react-email/components/* to the shipped src/ (reaches into private internals), or eat the +190 KB. None of these is something to recommend.

@react-email/editor itself is the canonical example of a consumer that ships these components to the browser, so this is an important use case for you all as well.

Proposal

Add subpath exports so consumers can do:

import { Body } from "react-email/components/body"
import { Img } from "react-email/components/img"
import { render } from "react-email/render"

Ideally with per-component dist entries + types, so each is fully tree-shakeable on its own. Happy to put up a PR if there’s interest in the direction.