How to use @react-email for tailwind styling?
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- react, tailwindcss, typescript
- Domain
- documentation, web-dev
Research direction
Start from the project's Cloudflare Workers entry point and reproduce the supplied @react-email template with the reported styling setup. Review the existing example structure first; done means the project contains a working @react-email example that can build and send an email from a Cloudflare Worker.
Written by the indexing model from the issue text.
Description
I installed the @react-email and necessary dependency, but the email template doesn't work on Cloudflare worker? Can you add some example on this project working with @react-email to build templates.
import { Button, Html } from "@react-email/components";
import * as React from "react";
export default function Email() {
return (
<Html>
<Button
href="https://example.com"
style={{ background: "#000", color: "#fff", padding: "12px 20px" }}
>
Click me
</Button>
</Html>
);
}
This the error, when I send any of the email -
- Dominant language
- TypeScript
- Stars
- 41
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from resend/resend-cloudflare-workers-example
-
Dependency DashboardOpen
Difficulty 5/5 Over a week Newbie friendliness 10/100
All issues in resend/resend-cloudflare-workers-example
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
code-yeongyu/senpi#7139 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
lingdojo/kana-dojo#34395 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
bug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mastra-ai/mastra#31093 · 1 comment ·
Maintainers usually reply within 1 day
-
area:web p2 product:business triage:active type:bug
Difficulty 1/5 Under an hour Newbie friendliness 89/100
cuadrao-ai/argus#2328 ·
Maintainers usually reply within 1 day
-
bug frontend good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
nikhilb2/simple_invoicing#907 ·