-
Notifications
You must be signed in to change notification settings - Fork 775
feat(root): development workflow for all components #2295
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.
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
base: canary
Are you sure you want to change the base?
feat(root): development workflow for all components #2295
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@react-email/body
@react-email/button
@react-email/code-block
@react-email/code-inline
@react-email/column
@react-email/components
@react-email/container
@react-email/font
@react-email/head
@react-email/heading
@react-email/hr
@react-email/html
@react-email/img
@react-email/link
@react-email/markdown
@react-email/preview
react-email
@react-email/render
@react-email/row
@react-email/section
@react-email/tailwind
@react-email/text
commit: |
0faf2a2
to
b63b211
Compare
This pull request adds a new package to the repository called
playground
that runs with the React Email's CLI directly and lets us write down any email template for testing, and also sets it up so that the hot reloading ofemail dev
is triggered by changes to any of the components.It also renames
dev
scripts on components tobuild:watch
to avoid any confusion for contributors, with also removing the rootdev
script which was meant for doing an equivalent, but less optimized, development workflow for components.The best side to this workflow is that it lets you copy over any email template and just experiment with things without having to worry about what to commit as everything is ignored. The other good thing is that it lets contributors play with multiple components at once.
It does not have any seeding because the good side to seeding would be to make sure a certain thing still works, and it is much better for us to do that through automated tests with vitest.
Development workflow
playground/emails/testing.tsx
with the contentspnpm dev
inplayground