36 feat refactoring email templates and implementing welcome email feature

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
formail-app	✅ Ready (Inspect)	Visit Preview	May 4, 2024 1:03pm

[socket-security[bot]]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@clerk/clerk-sdk-node@4.13.16	environment Transitive: filesystem, network	+54	9.34 MB	nikosdouvlis
npm/@clerk/nextjs@4.30.1	Transitive: environment, network	+30	10.5 MB	nikosdouvlis
npm/@clerk/themes@1.7.14	None	+3	1.62 MB	nikosdouvlis
npm/@react-email/components@0.0.17	Transitive: environment, filesystem, network, shell	+80	17.4 MB	gabrielmfern
npm/@sentry/nextjs@7.113.0	environment, filesystem, network Transitive: eval, shell, unsafe	+138	40.4 MB	sentry-bot
npm/@tabler/icons-react@3.3.0	None	+1	43.9 MB	codecalm
npm/@types/node@20.12.8	None	+1	2.13 MB	types
npm/convex@1.11.3	Transitive: environment, filesystem, network, shell	+37	229 MB	ballingt
npm/posthog-js@1.130.2	None	+2	8.43 MB	timgl
npm/react-email@2.1.2	Transitive: environment, eval, filesystem, network, shell, unsafe	+367	1.83 GB	gabrielmfern
npm/svix@1.23.0	network	+12	2.72 MB	svixdev
npm/zod@3.23.6	None	0	666 kB	colinmcd94

🚮 Removed packages: npm/@clerk/clerk-sdk-node@4.13.15, npm/@clerk/nextjs@4.30.0, npm/@clerk/themes@1.7.13, npm/@sentry/nextjs@7.112.2, npm/@tabler/icons-react@3.2.0, npm/@types/node@20.12.7, npm/convex@1.11.2, npm/posthog-js@1.130.0, npm/react-hook-form@7.51.3, npm/svix@1.21.0, npm/zod@3.23.4

View full report↗︎

[socket-security[bot]]

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/@swc/core@1.3.101

View full report↗︎

Next steps

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

[seangray-dev]

@SocketSecurity ignore npm/@swc/core@1.3.101