<Head> is outside <Tailwind>d0a7a52: Move all components and utilities into the react-email package
All components (previously in @react-email/components or individual packages like @react-email/button) and rendering utilities (previously in @react-email/render) are now exported directly from react-email. This unifies the install and import experience into a single package.
We're going to deprecate all packages except @react-email/render and @react-email/ui, and they will not be updated anymore.
Imports from @react-email/components, @react-email/render, or individual component packages (e.g. @react-email/button) are no longer the recommended path and they will all be deprecated with the exception of @react-email/render and @react-email/editor, and render will remain exported from react-email. Consumers should import everything from react-email.
Having separate packages for components (@react-email/components), and the CLI (react-email) created unnecessary confusion, and a maintenance burden for us.
Remove @react-email/components:
npm remove @react-email/componentsUpdate react-email, and move it over to dependencies:
npm install react-email@latestUpdate your imports:
- import { Button, Html, Head, render } from "@react-email/components";
+ import { Button, Html, Head, render } from "react-email";url.parse() with WHATWG URL API in the preview dev server.d0a7a52: Move all components and utilities into the react-email package
All components (previously in @react-email/components or individual packages like @react-email/button) and rendering utilities (previously in @react-email/render) are now exported directly from react-email. This unifies the install and import experience into a single package.
We're going to deprecate all packages except @react-email/render and @react-email/preview-server, and they will not be updated anymore.
Imports from @react-email/components, @react-email/render, or individual component packages (e.g. @react-email/button) are no longer the recommended path and they will all be deprecated with the exception of @react-email/render and @react-email/editor, and render will remain exported from react-email. Consumers should import everything from react-email.
Having separate packages for components (@react-email/components), and the CLI (react-email) created unnecessary confusion, and a maintenance burden for us.
Update your dependencies -- remove @react-email/components, keep react-email:
- npm install @react-email/components react-email @react-email/preview-server
+ npm install react-email @react-email/preview-serverUpdate your imports:
- import { Button, Html, Head, render } from "@react-email/components";
+ import { Button, Html, Head, render } from "react-email";The @react-email/preview-server and @react-email/editor packages are not included in react-email
url.parse() with WHATWG URL API in the preview dev server.$HOME/.react-emailemail build always failingemail buildstyleText from node:util instead of chalkexport when without manual React importemail dev on Windowsrender versions<svg> not being flagged as incompatiblecolor-scheme: dark for the previewNodeNext-style importsrequire in email exportimport ... = require(...) syntaxemail dev not working with traversal errorrender versionsstatic directoryexport's esbuild failsdeno not working as an option for email buildnext@15.2.4next@15.2.3punycode package for the static modulesemail devemail devemail dev19cab7b: Fixes decorators causing dependency tree babel parsing to fail
14b7d1d: update socket.io/socket.io-client to 4.7.5
b68e166: Fix sharp warning when running email dev
3caaf53: Updated peer dependencies to allow for React 19 release candidated and React 19 itself
9a5fd78: fix email template preview failing with emails having spaces
d118a39: Fixes tooltip color being black for specific theming configurations
481e339: Fixes root directories being hidden when they are alone at their depth
f9483ec: Deprecated renderAsync and made render itself always async
Three reasons:
See https://github.com/resend/react-email/discussions/1144 for more info.
If you are using the old render, you will need to now treat the Promise
that comes out of it, as it is now async. If you are using renderAsync,
you can replace it with render and things should work the same.
email devemail dev2799bb4: fix email template preview failing with emails having spaces
3f67038: Deprecated renderAsync and made render itself always async
Three reasons:
See https://github.com/resend/react-email/discussions/1144 for more info.
If you are using the old render, you will need to now treat the Promise
that comes out of it, as it is now async. If you are using renderAsync,
you can replace it with render and things should work the same.
emails directoryemails directory