Why Custom store logic in Svelte? - Purpose & Use Cases

The Big Idea

What if your app could handle all the boring updates for you, perfectly every time?

The Scenario

Imagine you have a shopping cart on a website and you want to update the total price every time someone adds or removes an item. Doing this by hand means you must watch every change and update the total yourself.

The Problem

Manually tracking changes is tiring and easy to mess up. You might forget to update the total or update it too late, causing wrong prices to show. It's like trying to keep score in a game without a scoreboard.

The Solution

Custom store logic in Svelte lets you create a smart container that watches changes and updates the total automatically. You write the rules once, and the store handles the rest, keeping your app neat and reliable.

Before vs After

✗ Before

let total = 0;
let items = [];
function addItem(price) {
  items.push(price);
  total = items.reduce((a, b) => a + b, 0);
}

✓ After

import { writable, derived } from 'svelte/store';
function createCart() {
  const store = writable([]);
  const { subscribe, update } = store;
  return {
    subscribe,
    addItem: (price) => update(items => [...items, price]),
    total: derived(store, $items => $items.reduce((a, b) => a + b, 0))
  };
}

What It Enables

It makes your app smarter and easier to maintain by automatically managing data changes and updates behind the scenes.

Real Life Example

Think of a music playlist app that updates the total playtime as you add or remove songs without you needing to recalculate it every time.

Key Takeaways

Manual updates are slow and error-prone.

Custom store logic automates data tracking and updates.

This leads to cleaner, more reliable apps.

Practice

1. What is the main purpose of creating a custom store in Svelte?

easy

A. To disable reactivity in the app

B. To add custom methods and control how data updates and shares

C. To make the store work only on the server side

D. To replace the built-in writable store completely

Solution

1. Step 1: Understand what a custom store does

   A custom store extends the basic writable store by adding your own methods to control data updates and sharing.

2. Step 2: Compare options with this understanding

   Only "To add custom methods and control how data updates and shares" correctly describes this purpose. The other options misunderstand the role of custom stores: disabling reactivity, replacing the built-in writable store completely, or server-side only.

3. Final Answer:

   To add custom methods and control how data updates and shares -> Option B

4. Quick Check:

   Custom store purpose = Add custom methods [OK]

Hint: Custom stores add your own methods to writable stores [OK]

Common Mistakes:

• Thinking custom stores replace writable stores entirely
• Believing custom stores disable reactivity
• Assuming custom stores only run on the server

2. Which of the following is the correct way to create a custom store in Svelte?

easy

A. import { writable } from 'svelte/store'; function createStore() { const { subscribe, update } = writable(0); return { subscribe, increment: () => update(n => n + 1) }; }

B. import { readable } from 'svelte/store'; function createStore() { const { subscribe } = readable(0); return { subscribe, increment: () => {} }; }

C. import { writable } from 'svelte/store'; function createStore() { const { subscribe, set } = writable(0); return { subscribe, increment: () => set(n => n + 1) }; }

D. import { store } from 'svelte/store'; function createStore() { return { subscribe: () => {}, increment: () => {} }; }

Solution

1. Step 1: Check import and store creation

   import { writable } from 'svelte/store'; function createStore() { const { subscribe, update } = writable(0); return { subscribe, increment: () => update(n => n + 1) }; } correctly imports writable and uses update to change the value.

2. Step 2: Verify method usage

   import { writable } from 'svelte/store'; function createStore() { const { subscribe, set } = writable(0); return { subscribe, increment: () => set(n => n + 1) }; } incorrectly uses set with a function argument, which is invalid. import { readable } from 'svelte/store'; function createStore() { const { subscribe } = readable(0); return { subscribe, increment: () => {} }; } uses readable which is read-only. import { store } from 'svelte/store'; function createStore() { return { subscribe: () => {}, increment: () => {} }; } imports a non-existent store.

3. Final Answer:

   import { writable } from 'svelte/store'; function createStore() { const { subscribe, update } = writable(0); return { subscribe, increment: () => update(n => n + 1) }; } -> Option A

4. Quick Check:

   Correct syntax uses writable and update() [OK]

Hint: Use writable and update() for custom store methods [OK]

Common Mistakes:

• Using set() with a function argument
• Using readable store when write access is needed
• Importing non-existent store types

3. Given this custom store code, what will be logged after calling counter.increment() twice?

import { writable } from 'svelte/store';
function createCounter() {
  const { subscribe, update } = writable(0);
  return {
    subscribe,
    increment: () => update(n => n + 1)
  };
}
const counter = createCounter();
counter.subscribe(value => console.log(value));
counter.increment();
counter.increment();

medium

A. 0, 1, 2

B. 1, 2

C. 0, 2

D. 2

Solution

1. Step 1: Understand subscription behavior

   Subscribing logs the current value immediately, so 0 is logged first.

2. Step 2: Trace increments and logs

   Each increment increases the value by 1 and triggers the subscriber, logging 1 then 2.

3. Final Answer:

   0, 1, 2 -> Option A

4. Quick Check:

   Subscription logs initial and updates [OK]

Hint: Subscription logs initial value immediately [OK]

Common Mistakes:

• Ignoring initial subscription log
• Assuming increments log only final value
• Confusing update with set behavior

4. Identify the error in this custom store code:

import { writable } from 'svelte/store';
function createTimer() {
  const { subscribe, set } = writable(0);
  let interval = null;
  return {
    subscribe,
    start: () => {
      interval = setInterval(() => set(n + 1), 1000);
    },
    stop: () => clearInterval(interval)
  };
}

medium

A. Not clearing interval on stop

B. Missing update method for incrementing

C. Using set(n + 1) without defining n

D. Incorrect import of writable store

Solution

1. Step 1: Check the setInterval callback

   The callback uses set(n + 1) but n is not defined anywhere in scope.

2. Step 2: Understand correct usage

   To increment the value, update should be used or the current value tracked. Using set with undefined n causes an error.

3. Final Answer:

   Using set(n + 1) without defining n -> Option C

4. Quick Check:

   Undefined variable in set() causes error [OK]

Hint: Use update() or track value before set() [OK]

Common Mistakes:

• Using set() with undefined variable
• Forgetting to clear intervals
• Confusing set and update methods

5. You want to create a custom store that holds a list of items and provides a method to add unique items only (no duplicates). Which implementation correctly achieves this?

hard

A. import { writable } from 'svelte/store'; function createList() { const { subscribe, update } = writable([]); return { subscribe, add: (item) => update(list => [...list, item]) }; }

B. import { writable } from 'svelte/store'; function createList() { const { subscribe, set } = writable([]); return { subscribe, add: (item) => set(list => list.includes(item) ? list : [...list, item]) }; }

C. import { readable } from 'svelte/store'; function createList() { const { subscribe } = readable([]); return { subscribe, add: (item) => {} }; }

D. import { writable } from 'svelte/store'; function createList() { const { subscribe, update } = writable([]); return { subscribe, add: (item) => update(list => list.includes(item) ? list : [...list, item]) }; }

Solution

1. Step 1: Check method to add unique items

   import { writable } from 'svelte/store'; function createList() { const { subscribe, update } = writable([]); return { subscribe, add: (item) => update(list => list.includes(item) ? list : [...list, item]) }; } uses update and checks if the item exists before adding, preventing duplicates.

2. Step 2: Verify other options

   import { writable } from 'svelte/store'; function createList() { const { subscribe, set } = writable([]); return { subscribe, add: (item) => set(list => list.includes(item) ? list : [...list, item]) }; } incorrectly uses set with a function argument, which is invalid. import { readable } from 'svelte/store'; function createList() { const { subscribe } = readable([]); return { subscribe, add: (item) => {} }; } uses readable which is read-only. import { writable } from 'svelte/store'; function createList() { const { subscribe, update } = writable([]); return { subscribe, add: (item) => update(list => [...list, item]) }; } adds items without checking duplicates.

3. Final Answer:

   Custom store with update() and duplicate check -> Option D

4. Quick Check:

   Use update() and check includes() for uniqueness [OK]

Hint: Use update() with includes() check to avoid duplicates [OK]

Common Mistakes:

• Using set() with function argument
• Using readable store when write access needed
• Not checking for duplicates before adding