4 ms·

https://svelte.dev/tutorial/basics https://svelte.dev/tutorial/basics - easy to get started with but really powerful for complex stuff too For layout, don't us

https://svelte.dev/tutorial/basics https://svelte.dev/tutorial/basics - easy to get started with but really powerful for complex stuff too For layout, don't use any CSS framework, but instead refer to https://css-tricks.com/snippets/css/a-guide-to-flexbox/ https://css-tricks.com/snippets/css/a-guide-to-flexbox/ often - every time I use some big CSS framework I end up fighting it at some point. https://vitejs.dev/ https://vitejs.dev/ for packaging - I got really grumpy when frontend stuff started needing build and packaging tools, but it's the nature of things so you just have to deal with it, and vite is fast, not overly complicated, and supports fast hot reloading.

jeanlucas 4y ago
I don't consider Svelte a simple toolset because it can't be published statically
- ramshorst 4y ago
  If you are in a larger scale SEO project this does blazing fast static generation with Svelte: https://github.com/Elderjs/elderjs https://github.com/Elderjs/elderjs
  - vonadz 4y ago
    Can attest to this. We used it to build https://findenergy.com https://findenergy.com which has over 15k pages and a TON of data.
- carbadtraingood 4y ago
  I think you are incorrect here. Sveltekit comes with a number of adapters designed to ship either a SSR site or a static SPA. Serving a static Svelte site is literally a one line change in a config file. I've got a good half dozen Svelte sites that live in s3.
- soggybutter 4y ago
  Unless I'm misunderstanding you, Svelte can absolutely be published statically. If you leverage SvelteKit and the SSR it offers, then yes you need to deploy a server, but regular Svelte builds a statically deployable bundle just like React, Vue, or any other big UI lib/framework
  - orangepanda 4y ago
    I think they meant that svelte cannot be used without a build step. The fact that builds dont need a second build is nice to know, even if useless.
- mateomorris 4y ago
  It can quite easily with https://primo.so https://primo.so
- Komodai 4y ago
  Have you even used Svelte yourself?
wackget 4y ago
Since when did frontend require building or packaging? In fact, since when did ANY web development require those things?
- plaguepilled 4y ago
  Why is that bad?
  - collyw 4y ago
    over complex mes
- collyw 4y ago
  Our front end devs were drawing diagrams of react components with arrows everywhere. All the app is doing are some fairly basic forms with a bit of validation. NPM install to get the thing running on a development machine, and it seems to download half of the internet. What an absolute shitshow "full stack" development is these days.

jeanlucas 4y ago

I don't consider Svelte a simple toolset because it can't be published statically

ramshorst 4y ago
If you are in a larger scale SEO project this does blazing fast static generation with Svelte: https://github.com/Elderjs/elderjs https://github.com/Elderjs/elderjs
- vonadz 4y ago
  Can attest to this. We used it to build https://findenergy.com https://findenergy.com which has over 15k pages and a TON of data.
carbadtraingood 4y ago
I think you are incorrect here. Sveltekit comes with a number of adapters designed to ship either a SSR site or a static SPA. Serving a static Svelte site is literally a one line change in a config file. I've got a good half dozen Svelte sites that live in s3.
soggybutter 4y ago
Unless I'm misunderstanding you, Svelte can absolutely be published statically. If you leverage SvelteKit and the SSR it offers, then yes you need to deploy a server, but regular Svelte builds a statically deployable bundle just like React, Vue, or any other big UI lib/framework
- orangepanda 4y ago
  I think they meant that svelte cannot be used without a build step. The fact that builds dont need a second build is nice to know, even if useless.
mateomorris 4y ago
It can quite easily with https://primo.so https://primo.so
Komodai 4y ago
Have you even used Svelte yourself?

wackget 4y ago

Since when did frontend require building or packaging? In fact, since when did ANY web development require those things?

plaguepilled 4y ago
Why is that bad?
- collyw 4y ago
  over complex mes
collyw 4y ago
Our front end devs were drawing diagrams of react components with arrows everywhere. All the app is doing are some fairly basic forms with a bit of validation. NPM install to get the thing running on a development machine, and it seems to download half of the internet. What an absolute shitshow "full stack" development is these days.