@DreaminDani is attempting to deploy a commit to the Svelte Team on Vercel.

A member of the Team first needs to authorize it.

Recommendations:

• https://www.puruvj.dev/blog/svelte-5-runic-persist-theming
• Paolo's response to my post: https://ricciuti.me/blog/effect-is-fine-but-proxies-are-better

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

Recommendations:

• https://www.puruvj.dev/blog/svelte-5-runic-persist-theming
• Paolo's response to my post: https://ricciuti.me/blog/effect-is-fine-but-proxies-are-better

Gentle reminder to add these 😅

@DreaminDani we will also have a bunch of svelte workshops in July at mainmatter...they are paid but I think it could be a good resource for svelte folks

https://mainmatter.com/events/?utm_source=svelte_newsletter&utm_medium=social&utm_campaign=25-06-25-how-to-build-web-components-with-svelte

Could you add this as well? https://x.com/puruvjdev/status/1938243522546503996

I mostly tested out the links and added a direct link to the project site instead of the GitHub

This works in most cases, but often times linking to the GitHub is much clearer to explain what an app and prevent folks from just immediately closing them. Like thom.chat (which I just added), for instance.

Anyway, I think this is ready to merge unless I missed something obvious in the changelogs :)

I mostly tested out the links and added a direct link to the project site instead of the GitHub

This works in most cases, but often times linking to the GitHub is much clearer to explain what an app and prevent folks from just immediately closing them. Like thom.chat (which I just added), for instance.

Oh I see. Should we default to linking to the GitHub repositories instead if they are available?

@eltigerchino I don't think we can make a rule that would work every time 😅 sometimes the GitHub link has more information, other times it's just the default SvelteKit README so it's actually less clear... I just choose on a case by case basis