Better-svelte-writable NPM

better-svelte-writable

license

This package provides a type-safe writable which gives you more control over the container.\ The writable is designed for you to painlessly replace with the native writable.

There are 3 problems this package is addressing:

You can't get the previous value after the value is changed.
Peeking the current value is not intuitive and verbose.
Syncing the value between multiple writables is not easy.

Installation
Demo
Highlight
Usage
Options
Changelog

Installation

$ npm i better-svelte-writable

Demo

Svelte RELP

Highlight

Previous tracking

This package letting you to keeps track as much as old values you need. [Option: trackerCount]

Value syncing

We provided native value syncing mechanism and it even works cross tabs. [Option: key] [Option: persist]

Simple getter

A light-weight getter is built-in in the BetterWritable<T, N> object. [Method: get]

Type-safety

The available previous tracker is strictly sized to trackerCount.

import { writable } from "better-svelte-writable";

const store = writable(0, { trackerCount: 2 });

{
  const [
    last,
    penultimate,
  ] = store.trackers;

  store.subscribe((current, last, penultimate) => {});
} // works

{
  const [
    last,
    penultimate,
    antepenultimate,
  ] = store.trackers;

  store.subscribe((current, last, penultimate, antepenultimate) => {});
} // ts(2493): Tuple type '[...]' of length '2' has no element at index '2'.

If you're using persistent writable, and the Zod schema is provided, the type of the value will be inferred from the schema.

import { writable } from "better-svelte-writable";

{
  const store = writable(0, {
    key: "test1",
    persist: {
      schema: z.number(),
    }
  });
} // works

{
  const store = writable(0, {
    key: "test2",
    persist: {
      schema: z.string(),
    }
  });
} // ts(2345): Argument of type 'number' is not assignable to parameter of type 'string'.

Usage

The writable from this package is a drop-in replacement for the native writable. It provides some additional features which are listed below. By simply replace svelte/store with better-svelte-writable in import statement, you can unlock the power of this package.

- import { writable } from 'svelte/store';
+ import { writable } from 'better-svelte-writable';

writable(value as T) is preferred over writable<T>(value), so types can be inferred automatically from schema.

import { writable } from 'better-svelte-writable';

const store = writable(0);

const {
  // Remaining the same as the native writable
  set,
  update,

  // New members
  get,          // a method for getting the current value without invoking the update
  trackers,     // an tuple which contains tracked previous values that can be used a store
                // only available when `trackerCount` is provided greater than 0
  previous,     // an tuple which contains the previous values
  toReadable,   // a method for converting the writable to a readable
  toComputed,   // a method for converting the writable to a computed

  key,          // a getter for the key option
  schema,       // a getter for the schema option
  previous,     // an tuple which contains the previous values
  overwrite,    // a getter for the overwrite option
  serializer,   // a getter for the serializer option
  isPersistent, // a boolean value indicates whether the value is persisted in storage

  // Modified
  subscribe,    // a method for subscribing to the value changes
} = writable(0);

// The `set`, `update`, `trackers` & `toReadable` are absent in the `BetterReadable<T>` object,
// rest of the members are exactly the same as the native `Readable<T>` object

`get`

The pain with the native writable is when you just need to peek the current value, the best you can do is through the update function and return the old value, or by using the provided get method in svelte/store. This is not only verbose but also not intuitive.

The solution we provide is a native get method inside the return BetterWritable<T> object which is much straight forward and performance friendly.

import { writable } from 'better-svelte-writable';

const store = writable(0);
console.log(store.get()); // 0

`trackers`

The trackers is an tuple which contains the BetterReadable<T> objects holding the previous values. Just like Readable<T> from svelte/store, the BetterReadable<T> object also has a subscribe method. By prefixing $, you can subscribe to the value changes.

The length of the tuple is determined by the trackerCount option.

<script lang="ts">
  import { writable } from 'better-svelte-writable';


  const store = writable(0, { trackerCount: 1 });
  const prev1 = store.trackers[0];
</script>

<div>Current : {$store}</div>
<div>Previous: {$prev1}</div>

<button on:click={() => $store++}>  +  </button>
<button on:click={() => $store=0}>Reset</button>
<button on:click={() => $store--}>  -  </button>

`previous`

The previous is an tuple which contains the previous values.

The length of the tuple is determined by the trackerCount option.

<script lang="ts">
  import { writable } from 'better-svelte-writable';

  const store = writable(0, { trackerCount: 1 });
  const prev1 = store.trackers[0];
</script>

<div>Current : {$store}</div>
<div>Previous: { prev1}</div>

<button on:click={() => $store++}>  +  </button>
<button on:click={() => $store=0}>Reset</button>
<button on:click={() => $store--}>  -  </button>

`toReadable`

The toReadable method is used to convert the BetterWritable<T> object to a BetterReadable<T> object. Which is a useful wrapper to discard the mutability and use the returned as a reference.

import { writable } from 'better-svelte-writable';

const store    = writable(0);
const readable = store.toReadable();

console.log(readable.get())

`toComputed`

The toComputed method is used to convert the BetterWritable<T> object to a BetterReadable<T> object. Which, when get or subscribe, will first compute the value from the function passed in.

import { writable } from 'better-svelte-writable';

const store    = writable(0);
const computed = store.toComputed(n => n * 2);

console.log(computed.get())

`isPersistent`

This is a simple boolean value that indicates whether the writable is persistent in storage.

import { writable } from 'better-svelte-writable';


const store1 = writable(0, { key: "test", persist: true  });
const store2 = writable(0, { key: "test", persist: false });

console.log(store1.isPersistent); // true
console.log(store2.isPersistent); // false

`subscribe`

The native subscribe method has one major problem, which has no way to found the old value when the callback is invoked. So the subscribe method we provide gives you the ability to see the old value(s). The first arg is the current value and followed by the previous values.

The length of the tuple is determined by the trackerCount option.

import { writable } from 'better-svelte-writable';


const store = writable(0, { trackerCount: 1 });

store.subscribe((current, last) => {
  console.log(last);
  console.log(current);
});

Options

writable<T> provides an optional second argument which is an object of options.

`trackerCount`

type trackerCountOption = number;

trackerCount decides how many previous values will be tracked. If this option is set to 0, the previous values will not be tracked.

The default value of trackerCount is 0.

import { writable } from "better-svelte-writable";


const store = writable(0, { trackerCount: 1 });

store.subscribe((n, last, penultimate) =>
  console.log(last, penultimate));


const last        = store.trackers[0];
const penultimate = store.trackers[1];

last       .subscribe(n => console.log("last"       , n));
penultimate.subscribe(n => console.log("penultimate", n));

`key`

type keyOption = string | undefined;

key can be used to sync the value between multiple writables. If the persist option is non-falsy, the value will also be synced across tabs.

If the key already exists, ALL the other options will be ignored.
The initialValue will be the fallback value if the key never been used.
There's no way stopping you from using 2 writable with same key but different type T.\ You need to make sure the type is the same manually.

The default value of key is undefined.

<script lang="ts">
  import { writable } from 'better-svelte-writable';


  const count1 = writable(0, { key: "count" });
  const count2 = writable(0, { key: "count" });
</script>

<div>Count1: {$count1}</div>
<div>Count2: {$count2}</div> <!-- also update when count1 changes -->

<button on:click={() => $count1++}>  +  </button>
<button on:click={() => $count1=0}>Reset</button>
<button on:click={() => $count1--}>  -  </button>

`isEqual`

type isEqualFunction = (currentValue: T, newValue: T) => boolean;

isEqual is the function which been used to compare the previous value with the new value, which can be customized to fit your needs.

The default value of isEqual is (a, b) => !safe_not_equal(a, b).

`forceEmit`

type forceEmitOption = boolean;

forceEmit indicates whether the callbacks will be called even if the value is not changed. If this option is set to true, the equality result of isEqual will be ignored.

The default value of forceEmit is false.

import { writable } from 'better-svelte-writable';


{
  const store = writable(0, { forceEmit: true });

  store.subscribe(() => console.log('fire'));

  store.set(1); // console: fire
  store.set(1); // console: fire
  store.set(1); // console: fire
}

{
  const store = writable(0, { forceEmit: false });

  store.subscribe(() => console.log('fire'));

  store.set(1); // console: fire
  store.set(1);
  store.set(1);
}

`start`

type setter  = (value: T) => void;
type updater = (fn: (value: T) => T) => T;

type startFunction = (set: setter, update: updater) => (void | () => void);

start is a function which is will be called when the first subscriber is added (not necessarily the first time).\ Which may return a function which will be called when the last subscriber is removed (not necessarily the last time).

The default value of start is () => {}.

import { writable } from 'better-svelte-writable';


const store = writable(0, {
  start: (set, update) => {
    console.log('start');
    return () => console.log('end');
  },
});


let tmp1 = store.subscribe(() => {}); // console: start
let tmp2 = store.subscribe(() => {});
let tmp3 = store.subscribe(() => {});

tmp2();
tmp3();
tmp1(); // console: end


let tmp4 = store.subscribe(() => {}); // console: start

tmp4(); // console: end

`persist`

interface Serializer<T> {
  parse    : (v: string) => T;
  stringify: (v: T     ) => string;
};

type persistOption<T> = boolean | {
  schema    ?: ZodType;
  storage   ?: Storage;
  overwrite ?: boolean;
  serializer?: Serializer<T>;
};

If persist is non-falsy, the key option must be set.

persist indicates whether or how will the value be stored in the storage. If this option is set to false, the value will only be stored in current tab. Otherwise, the value will be stored in the storage, which will be synced across tabs with the writables with the same key.

2 sub-options are available:

storage: The storage to be used.\ The default value of storage is localStorage.
serializer: The serializer to be used.\ The default value of serializer is JSON.
schema: The validator checking if value is invalid created with Zod.\ The default value of schema is undefined.
overwrite: Whether the value in the storage will be overwritten when invalid.\ > "always" Overwritten whenever storage value is invalid then warn in console\ > "initial" Only overwrite when value is invalid on creation\ > "never" Never overwrite and throw error when value is invalid\ The default value of overwrite is "never".

The default value of persist is false.

<!-- /+page.svelte -->
<script lang="ts">
  import { writable } from 'better-svelte-writable';
  const count = writable(0, { key: "count", persist: true });
</script>

<!-- Value been sync across tabs -->
<div>Count: {$count}</div>

<button on:click={() => $count++}>  +  </button>
<button on:click={() => $count=0}>Reset</button>
<button on:click={() => $count--}>  -  </button>

svelte sveltejs writable

zod

@everything-registry/sub-chunk-1229

10 months ago

10 months ago

10 months ago

10 months ago