2022-11-16
1382
#svelte
Raphael Ugwu
15942
Nov 16, 2022 ⋅ 4 min read

Application state management with Svelte

Raphael Ugwu Writer, software engineer, and a lifelong student.

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

5 Replies to "Application state management with Svelte"

  1. Thank you for the solid explanation of a use-case for stores in Svelte.

    I recently started going through the Svelte documentation, and this really helped me tie things together in my mental model for how stores can be used.

  2. Thanks great guide, just please fix the error in the function:

    “`
    const addCar = car => update(car => {
    return […cars, car];
    });
    “`

    Should be:
    “`
    const addCar = cars => update(car => {
    return […cars, car];
    });
    “`

  3. Guys you got this backwards. addCar() should take a parameter of car (singular) and update should take cars (plural). Should be like this:

    const addCar = car => update(cars => {
    return […cars, car];
    });

Leave a Reply