chore(tailwind): add peer dependencies as dev dependencies

[gabrielmfern]

I noticed the tests were failing in https://github.com/resend/react-email/actions/runs/21145041455/job/60816878885?pr=2858 because it wouldn't build the peer dependencies of @react-email/tailwind which was causing the errors to fail, this pull requests adds them in which, after running pnpm turbo test --filter="[HEAD^1]" locally, I can confirm it does work.

---

Summary by cubic

Add missing @react-email peer dependencies to @react-email/tailwind as devDependencies to ensure peers build during tests and prevent failures.

• Dependencies
  • Added: @react-email/body, @react-email/code-block, @react-email/code-inline, @react-email/container, @react-email/img, @react-email/preview, @react-email/text.

^{Written for commit fa3e22a. Summary will update on new commits.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: fa3e22a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Review	Updated (UTC)
react-email	Ready	Preview, Comment	Jan 19, 2026 7:01pm
react-email-demo	Ready	Preview, Comment	Jan 19, 2026 7:01pm

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	normalize-path@​3.0.0
	clsx@​2.1.1
	prompts@​2.4.2
	log-symbols@​4.1.0
	ora@​5.4.1
	punycode@​2.3.1
	chokidar@​4.0.3
	react@​19.0.0
	tsconfig-paths@​4.2.0
	react-dom@​19.0.0

View full report

[cubic-dev-ai]

No issues found across 1 file

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: pnpm-lock.yaml → npm/safer-buffer@2.1.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/safer-buffer@2.1.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/resend/react-email/@react-email/tailwind@2864

commit: fa3e22a