Astro vs Vite

Parent context: What purpose does astro serve if everything is vanilla Reply: Tons! Content collections, components, and layouts all make my workflow and organization much, much simpler while still allowing me the joy and simplicity of writing vanilla code. That's really the gift that is Astro—I get the benefits of a framework but absolutely nothing is any more complicated than I personally want it to be.

Went with Astro deployed to Cloudflare and immensely appreciated that I was mostly able to stick to just writing plain ol' vanilla HTML, CSS, and JS for the whole thing.

Next (and other meta-frameworks like Astro and Sveltekit) are great as BFFs.

Great work! Astro is such a breath of fresh air for sites that don’t need a heavy JS runtime.

I love it for SPA’s too! You can use anything you can use in an SPA that you can do with a normal app — just put it all in index.astro

I enjoyed the great DX from tools like Vite, Docker, and Swagger APIs

So we offloaded CMS duties to WordPress and used Vite for our actual app.

Well Vite is an amazing bundler.

I hate to be that guy, but we don't really use CRA anymore. Even the Facebook devs say to use Vite.

What were you configuring? Starting a Vite project with all those libs takes maybe 5-10 minutes at most?