Introduction to Svelte
daveceddia.com
Introduction to Svelte
1–10 of 116 posts
Re: Introduction to Svelte
#2I've been building something with Svelte 3 for about 6 months now.
- As should be clear in the article, it's very easy to pick up. In the first couple of weeks I got compiler errors, and kept having to look at how props and binding worked in the tutorial, but now I just make components without having to really think about Svelte.
- TS support is on the way (yaay)
- I'd like to know more about server-side rendering on Lambda - ie, Sapper currently wants to use something persistent like Express, but that really shouldn't be necessary.
Re: Introduction to Svelte
#3This looks much more germane to the Web than the other frameworks du jour. Will be interesting to see how it develops, but this was a pretty interesting look at how it works.
Re: Introduction to Svelte
#4> Another nice thing: the node_modules folder for this Hello World Svelte app totals only 29MB and 242 packages
"Only".
Re: Introduction to Svelte
#5I loved Svelte a few years back and still think it's a nice framework with cool ideas. However, a big issue for me using it at a company is that testing (especially unit testing) seems to be an afterthought. This has made it a non-starter for using it with multiple teams working on same code base. Maybe it's changed with Svelte 3 but a library I wrote for it wasn't clear how to test.
(Edit sounds same: https://github.com/sveltejs/svelte/wiki/FAQ#how-do-i-do-test...)
JS libraries sometimes take a non-presciptive approach of "test however you want!", But roll your own testing for a UI framework really limits adoption and enthusiasm at larger companies.
Re: Introduction to Svelte
#6I loved Svelte a few years back and still think it's a nice framework with cool ideas. However, a big issue for me using it at a company is that testing (especially unit testing) seems to be an afterthought. This has made it a non-starter for using it with multiple teams working on same code base. Maybe it's changed with Svelte 3 but a library I wrote for it wasn't clear how to test. (Edit sounds same: https://github…
Did you look at svelte-testing-library[1]? It looks like a good option to me, but I haven’t tried it.
1: https://github.com/testing-library/svelte-testing-library
Re: Introduction to Svelte
#7> Another nice thing: the node_modules folder for this Hello World Svelte app totals only 29MB and 242 packages "Only".
That's the compiler, not the output of the compiler.
Likewise GCC/LLVM is huge, but helloworld.bin is pretty small.
Re: Introduction to Svelte
#8I loved Svelte a few years back and still think it's a nice framework with cool ideas. However, a big issue for me using it at a company is that testing (especially unit testing) seems to be an afterthought. This has made it a non-starter for using it with multiple teams working on same code base. Maybe it's changed with Svelte 3 but a library I wrote for it wasn't clear how to test. (Edit sounds same: https://github…
Did you look at svelte-testing-library [1]? It looks like a good option to me, but I haven’t tried it. 1: https://github.com/testing-library/svelte-testing-library
Ah that looks nice, will try it out, thank you!
Re: Introduction to Svelte
#9> Another nice thing: the node_modules folder for this Hello World Svelte app totals only 29MB and 242 packages "Only".
The project I'm working on with only a couple web components using Angular already exceeded 400MB node_modules folder. Web development sometimes freak me out.
Re: Introduction to Svelte
#10This looks much more germane to the Web than the other frameworks du jour. Will be interesting to see how it develops, but this was a pretty interesting look at how it works.
Ins't /Svelte/ the framework du jour? :)