Gatsby VS Svelte

That's all we need todo to run our Medusa server locally. Medusa provides different storefronts which are based on Gatsby or Next.js we'll cover in later parts howto setup a storefrontend.

Gatsby as a static site generator

Node is basically back-end Javascript. While powerful alone, almost exclusively you will use a back-end framework like Next.js or Gatsby when using React, and then maybe Nuxt or Gridsome in Vue.

Tools and Frameworks such as Gatsby, Nextjs, Hugo are great choices for creating static sites.

If you want to build static website, use headless Wordpress and Graphql then I'd go for Gatsby

15. Gatsby

When I decided to rewrite my blog, one of the reasons was that I wanted to learn more about NextJS. It had already gotten some traction then, and seemed like a good fit for a blog. It was a bit overkill compared to other solutions like Gatsby, but I liked the idea of learning something that would allow me to quickly create even more complicated prototypes thanks to API routes.

Gatsby has ~54 000 Github stars and ~4 000 contributors. Its handles high-traffic sites extremely well. That’s why Cloudflare is based on Gatsby.

Recently, I revamped my blogging site from Gatsby to NextJS.

4. Static sites builders There are many static site builder tools for every framework possible, and others like Hugo and Jekyll. My go to pick is GatsbyJS

Sadly this is not possible right now. There is a discussion going on Github, but the issue is related to many other cases, you can follow the discuttion here: https://github.com/sveltejs/svelte/issues/4079

First I wanted to update my tools, maybe I just needed a small patch instead of changing them. So I made a project for a client using Laravel, Inertia.js Svelte, and then other project using Laravel, Inertia and React. I liked Svelte over React, so if future frontend projects appear, my main tool would be Svelte.

- Github thread 1

Looking at svelte specifically the first few I opened don’t have a reproduction. Didn’t check Kit. But even some with a reproduction like https://github.com/sveltejs/svelte/issues/8207 are just straight user error. Not trying to use this one issue to say all are junk but there is a fair amount of junk in the main svelte issues.

There are nearly 1100 open issues across two main repos: 749 in sveltejs/svelte and 343 in sveltejs/kit. And it's not like they're some junk issues, quite a bit of issues thoroughly report a bug.

Svelte was born in 2016, and it is an open-source front-end framework. On this website, we can clearly understand why this framework was born.

React is bloated garbage created by BoomerChan and its popularity is waning. Vue is much better to work with, and you should also check out Svelte.js a well.

Also, regarding the "multiple components in one file" problem, I wondered this aswell. Especially for prototyping, this would be nice. There is this, but I have never used it, and also this discussion.