Skip to content
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

blog: "What's new in Svelte" May newsletter #469

Merged
merged 5 commits into from
May 2, 2023

Conversation

DreaminDani
Copy link
Contributor

I was thinking we could mention the hackathon winner in the intro

@vercel
Copy link

vercel bot commented Apr 22, 2023

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

Name Status Preview Comments Updated (UTC)
hn ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 2, 2023 7:37am

@vercel
Copy link

vercel bot commented Apr 22, 2023

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

A member of the Team first needs to authorize it.

@baseballyama
Copy link
Member

I would like to mention about default ESLint changing if we can merge this PR before shipping the newsletter.

sveltejs/kit#9749

@kevmodrome
Copy link
Contributor

Winner won't be announced until May 6th at Svelte Summit so maybe it's better to put info about that in the next one? I suspect maybe we'd want to write a separate blog post about that also 🤔

@DreaminDani
Copy link
Contributor Author

@dummdidumm and/or @benmccann I think this is ready to merge :)

Copy link
Member

@dummdidumm dummdidumm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One question to Kev, rest is stellar as always

Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>
@paoloricciuti
Copy link
Member

We also presented https://sveltelab.dev in the site showcase if you want to add it 😊

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants