2023-09-18
2403
#astro#svelte
Elijah Asaolu
178111
109
Sep 18, 2023 ⋅ 8 min read

Exploring Astro and Svelte vs. SvelteKit: A comparative guide

Elijah Asaolu I am a programmer, I have a life.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 ⋅ 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 ⋅ 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 ⋅ 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 ⋅ 12 min read
View all posts

7 Replies to "Exploring Astro and Svelte vs. SvelteKit: A comparative guide"

  1. I am assuming there’s a typo error in the command given to install Tailwind CSS in Astro.

    …install Tailwind CSS by running the following command:

    npx astro add svelte
    # OR
    yarn astro add svelte

    I hope someone would notice my comment and fix this.

    1. It seems by legacy he means legacy as per work received by someone. For example if I just accepted to work in a software company, there is high probability that I would continue someone’s work. One might be some application that is already running, here I call it legacy.

  2. Hi, if you say to select for astro project you should consider you will not have the layout folder and file.

Leave a Reply