svelte-kit-koa-boilerplate
svelte-error-boundary
svelte-kit-koa-boilerplate | svelte-error-boundary | |
---|---|---|
1 | 3 | |
3 | 72 | |
- | - | |
5.0 | 0.0 | |
about 3 years ago | over 2 years ago | |
TypeScript | JavaScript | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
svelte-kit-koa-boilerplate
-
My Evaluation of SvelteKit for Full-Stack Web App Development
- once released and popular, they cease getting frequent updates
Now, yes this is a generalization. It doesn't apply to all of their packages, and not at the same point in time. But there is a pattern there. Some quick diving into the author's Github account, and their more popular repos shows the pattern. It's also clear that this was a choice made by a Svelte contributor to use their own package for "official" support in Svelte Kit.
When it comes to polka itself, I just don't get why a maturing framework like Svelte would choose something whose only real advantage lies in micro-benchmarking porn [1]. Speculation aside, I'm surprised the Svelte team didn't look at that choice through a lens of higher scrutiny. Koa would have been an infinitely better choice in my personal opinion, and there are several community-driven setups [2][3] for it.
[1] https://github.com/lukeed/polka#benchmarks
[2] https://github.com/kaladivo/svelte-kit-koa-boilerplate
[3] https://blog.logrocket.com/sapper-svelte-tutorial-2021/
svelte-error-boundary
-
Now that SvelteKit 1.0 is out, what would you like to see added to its ecosystem? What would make your life easier / take a part of its functionality the extra mile?
Apparently it's quite a complex problem from what I have gathered. While there are packages like @crownframework/svelte-error-boundary that can guard from initialization-time errors, which I have blogged about, they sometimes don't work with asynchronous errors or errors triggered in child components. So it would actually be huge to have built-in support for error boundaries.
-
My Evaluation of SvelteKit for Full-Stack Web App Development
I agree with you error boundaries are a huge omission. You can do basic error boundaries using one of these two packages:
* https://github.com/crownframework/svelte-error-boundary
-
Error Boundaries in Svelte
Thankfully there is a community package available that implements error boundaries! 🤩
What are some alternatives?
svelte-it-will-scale - Generate a chart showing svelte's overhead
svelte-error-boundary - Fix error boundary Svelte 3 problem to prevent full app crash :scream: