Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Fix react-email dev server #3263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
steven-tey wants to merge 1 commit into from
Closed

Fix react-email dev server #3263

steven-tey wants to merge 1 commit into from
+146 −4

Conversation

@steven-tey
Copy link
Collaborator

@steven-tey steven-tey commented Dec 21, 2025 •
edited by coderabbitai bot
Loading

Summary by CodeRabbit

  • Chores
    • Reorganized email package dependencies to optimize development setup.

✏️ Tip: You can customize this high-level summary in your review settings.

@vercel
Copy link
Contributor

vercel bot commented Dec 21, 2025 •
edited
Loading

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

Project Deployment Review Updated (UTC)
dub Ready Ready Preview Dec 21, 2025 8:11pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 21, 2025 •
edited
Loading

Walkthrough

Dependency configuration update for the email package. Moved "react-email" from production dependencies to development dependencies and added "@react-email/preview-server" as a development dependency.

Changes

Cohort / File(s) Change Summary
Email package dependencies
packages/email/package.json		 Moved react-email from dependencies to devDependencies; added @react-email/preview-server to devDependencies

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

  • Single file change with no logic modifications
  • Straightforward dependency reorganization
  • No functional impact on codebase behavior

Possibly related PRs

  • Bump react-email + resend deps #3260: Modifies the same packages/email/package.json file to bump or adjust react-email-related packages, complementing this PR's dependency management changes

Poem

🐰 A hop, a skip, a dep-confess,
React-email moves with finesse,
Dev tools bundled, sharp and clean,
Preview server now on scene!
Dependencies sorted, no more mess!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Fix react-email dev server' directly relates to the changeset's main objective of reorganizing react-email dependencies to fix the dev server setup.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch react-email-dev
📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 854a16e and 02c4f2c.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • packages/email/package.json (1 hunks)
🧰 Additional context used
🧠 Learnings (1)
📓 Common learnings 
Learnt from: steven-tey
Repo: dubinc/dub PR: 2958
File: apps/web/app/app.dub.co/(dashboard)/[slug]/settings/members/page-client.tsx:432-457
Timestamp: 2025-10-15T01:05:43.266Z
Learning: In apps/web/app/app.dub.co/(dashboard)/[slug]/settings/members/page-client.tsx, defer refactoring the custom MenuItem component (lines 432-457) to use the shared dub/ui MenuItem component to a future PR, as requested by steven-tey.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build
🔇 Additional comments (1)
packages/email/package.json (1)

21-21: Good architectural fix—versions verified as current and secure.

Moving react-email to devDependencies is correct since it's a CLI tool for development. Adding @react-email/preview-server explicitly aligns with the v5.x architecture where the preview server is installed separately. Both packages are at version 5.1.0 (the latest stable release) with no security advisories. Verified that no production code in packages/email/src/ imports react-email directly—only the dev script uses the CLI, and all runtime email functionality is provided by @react-email/components, @react-email/render, and resend in dependencies.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@socket-security
Copy link

socket-security bot commented Dec 21, 2025

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

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Added@​react-email/​preview-server@​5.1.0941008698100

View full report

@socket-security
Copy link

socket-security bot commented Dec 21, 2025

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 High
Obfuscated code: npm @react-email/preview-server is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: packages/email/package.json → npm/@react-email/[email protected]

ℹ 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 [email protected].

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/@react-email/[email protected]. 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

@steven-tey steven-tey closed this Dec 21, 2025
@steven-tey steven-tey deleted the react-email-dev branch December 21, 2025 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@steven-tey