benmccann

I got straight 100s using SvelteKit on https://c3.ventures

I used Gemini to compare the minimized output of the Rollup vs Rolldown JavaScript bundlers to find locations where the latter was not yet at the same degree of optimization. It was astoundingly good and I'm not sure how I would have been able to accomplish the task without an LLM as an available tool.

fixed!

Hundreds of people had access to publish the Zapier SDK, so it's little surprise they were eventually compromised! (https://bsky.app/profile/benmccann.com/post/3m6fdecsbdk2u)

The e18e community are reducing dependencies in popular libraries and building tools to prevent and reduce the impact of such attacks. Join if you want to help out! https://e18e.dev/

Just this morning, after trying to make the case over the past year, we had a change landed to remove more than a dozen dependencies from typescript-eslint! https://bsky.app/profile/benmccann.com/post/3m6fcjax7ec2h

Yes, eslint is particularly frustrating: https://npmgraph.js.org/?q=eslint

There are plenty of people in the community who would help reduce the number of dependencies, but it really requires the maintainers to make it a priority. Otherwise the only way to address it is to switch to another solution like oxlint.

The number 3, 4, and 5 contributors to SvelteKit in the past year work at Vercel: https://github.com/sveltejs/kit/graphs/contributors?from=8%2...

Rich and Simon are incredibly important, but they're in it for Svelte and the community more so than a paycheck from Vercel. Tee has been doing most of the maintenance on SvelteKit currently funded by community donations. And this isn't counting other infrastructure like vite-plugin-svelte or the Svelte CLI which are entirely maintained by volunteers. I don't think Vercel funds a majority of the work on Svelte even if it might be close to it.

Only 3/40 Svelte maintainers work at Vercel and they mainly finance work on Svelte core. SvelteKit day-to-day is primarily maintained by folks outside Vercel

Wouldn't vouch proxy only work with self hosted apps? How would you use it with a SaaS app?

What is the plastic.love you're referring to? That domain doesn't resolve for me. Do you mean PlasticList?

It's neither true that Svelte has few users or that we can easily break things. Tons of sites are built with Svelte like Yahoo Finance and Apple Music. Svelte 5 was the only big change in syntax in the past five years and we made sure that there's a good migration tool, etc. to minimize the amount of hardship and upgrade might cause. As a result the majority of users have already upgraded to Svelte 5.

That being said, Svelte absolutely does continue to innovate. We'll be introducing a new async primitive, RPC mechanism, etc. in the near future: https://m.youtube.com/watch?v=1dATE70wlHc

The updated knowledge cutoff is helping with new technologies such as Svelte 5.

NextAuth certainly needs some competition. However, I wish better-auth didn't have so many dependencies. I feel like it shouldn't be necessary to depend on things like kysley and Typescript.

Check out https://www.perceptive.io/

I believe the reason for that was to enable event forwarding, which was a highly requested feature and makes a lot of things easier.

The docs for single page apps live at https://svelte.dev/docs/kit/single-page-apps

By default, SvelteKit does SSR for the first page and client-side routing thereafter. This is fully configurable. Perhaps it's worth an additional mention on the routing page. I'll take a look later. Thanks for the suggestion.

You should only access credentials in `.server` files. We have a built-in feature that checks that you only access credentials in `.server` files to try to prevent newcomers from accidentally making any mistake in that regard.

Actually, I forgot that this landed as an official part of the docs now: https://svelte.dev/docs/llms

It might still be a bit big, but PRs welcome if folks want to try slimming it down to just the stuff that's new in Svelte 5.

I haven't used Claude much personally, but have seen https://svelte-llm.khromov.se/ built to help on that front, do you might want to check it out.

Vite does statically replace the `browser` variable with `true` or `false` based on whether you're on the client or server, but this shouldn't affect the correctness of your code. It does allow Vite to remove any unused code, however. E.g. `if (browser)` turns into `if (false)` on the server and any code within that block can be removed. This can avoid shipping unused code to the client.

Astro is also built in top of Vite and the same thing happens there. If you reference `import.meta.env.SSR` it is statically replaced during build and unused code is tree-shaken out: https://vite.dev/guide/env-and-mode#env-variables

Files with `.server` in the name run only on the server. The remaining files run on the client and server. This is mentioned in the introduction on https://svelte.dev/docs/kit/routing

What's confusing about this and what could we do to help?

Snippets are far more powerful than slots and so the change is not merely cosmetic. Snippets give you a way to create reusable HTML fragments within a component.

The v3/v4 docs can be found at https://v4.svelte.dev/

There is a migration guide as well as a migration tool that will migrate most of your code for you. You can also see what an individual file looks like when migrated in the playground.

Svelte is doing its own Advent of Code challenge with a twist this year. Instead of challenging users, the maintainers will be challenging themselves to launch one feature a day. Today's feature is error boundaries!

https://bsky.app/profile/svelte.dev/post/3lcavobxn7c2k

JAWSM might be a more unique alternative if you're looking for any.

Anyway, it's a cool project. Thanks for sharing!

shadcn-svelte is great!!

https://www.skeleton.dev/ and https://flowbite-svelte.com/ are another couple of popular ones.

There's a big list at https://www.sveltesociety.dev/packages?category=design-syste...

The old syntax is considered legacy and it is recommended to upgrade. There is a migration tool to do most of it automatically for you.

Hopefully just adding those two lines to your project once isn't an issue. We'll try to address any remaining difficulties as part of SvelteKit 3. (e.g. this issue which I added to the 3.0 milestone: https://github.com/sveltejs/kit/issues/12580)

What software is that?

Insurance companies may be more likely to cover home sleep studies, which cost less to run and are nearly as effective. A sleep doctor should be able to pre-authorize the study with the insurance company.

If you want to do it yourself without going through insurance you could check out Wesper. You can also buy a Wellue O2Ring off Amazon and see if your oxygen saturation ever drops overnight, which is a large part of what Wesper does.