Dependency Dashboard
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- nextjs, react, tailwindcss, typescript
Research direction
Start with the linked Dependency Dashboard documentation and inspect package.json and pnpm-workspace.yaml. The listed updates are already represented by linked Renovate pull requests, while other updates are rate-limited or require dashboard actions. A specific dependency update and its completed checks would be needed to define done.
Written by the indexing model from the issue text.
Description
This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.
View this repository on the Mend.io Web Portal.
Rate-Limited
The following updates are currently rate-limited. To force their creation now, click on a checkbox below.
- fix(deps): update react-email monorepo to v6.11.16 (
@react-email/ui,react-email) - chore(deps): update dependency @types/node to v26
- chore(deps): update dependency typescript to v7
- chore(deps): update pnpm to v12
- 🔐 Create all rate-limited PRs at once 🔐
Open
The following updates have all been created. To force a retry/rebase of any, click on a checkbox below.
- chore(deps): update dependency postcss to v8.5.23 [security]
- fix(deps): update dependency next to v16.4.5 [security]
- fix(deps): update dependency sonner to v2.0.8
- chore(deps): update dependency @biomejs/biome to v2.6.8
- chore(deps): update dependency @types/node to v24.19.2
- chore(deps): update dependency autoprefixer to v10.7.0
- chore(deps): update dependency typescript to v5.9.3
- chore(deps): update pnpm to v11.28.13
- chore(deps): update tailwindcss monorepo to v4.3.5 (
@tailwindcss/postcss,tailwindcss) - fix(deps): update dependency resend to v4.8.0
- fix(deps): update react monorepo (
@types/react,@types/react-dom,react,react-dom) - fix(deps): update dependency resend to v6
- Click on this checkbox to rebase all open PRs at once
Detected Dependencies
npm (1)
package.json (18)
@react-email/ui 6.0.0→ [Updates:6.11.16]clsx 2.1.1next 16.2.9→ [Updates:16.4.5]react 19.2.7→ [Updates:19.3.1]react-dom 19.2.7→ [Updates:19.3.1]react-email 6.0.0→ [Updates:6.11.16]resend 4.6.0→ [Updates:4.8.0,6.39.0]sonner 2.0.6→ [Updates:2.0.8]@biomejs/biome 2.0.6→ [Updates:2.6.8]@tailwindcss/postcss 4.1.11→ [Updates:4.3.5]@types/node 24.0.8→ [Updates:24.19.2,26.6.6]@types/react 19.2.17→ [Updates:19.3.0]@types/react-dom 19.2.3→ [Updates:19.3.0]autoprefixer 10.4.21→ [Updates:10.7.0]postcss 8.5.6→ [Updates:8.5.23]tailwindcss 4.1.11→ [Updates:4.3.5]typescript 5.8.3→ [Updates:5.9.3,7.0.2]pnpm 11.3.0→ [Updates:11.28.13,12.21.0]
- Check this box to trigger a request for Renovate to run again on this repository
- Dominant language
- TypeScript
- Stars
- 84
- Forks
- 25
- 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-vercel-example
-
Vercel Build FailsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
All issues in resend/resend-vercel-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 ·