npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

svelte-immer-store

v1.0.4

Published

Svelte compatible store using immutable immer objects

Downloads

2,971

Readme

svelte-immer-store

Svelte compatible store using immutable immer objects

See:

trunk

Installation

npm install svelte-immer-store

OR

pnpm install svelte-immer-store

OR

yarn install svelte-immer-store

Features

  • Provides automatic immutable state management
  • Immutable state allows the usage of <svelte:options immutable={true}/> (see REPL)
  • Allows for simple change history tracking (undo/redo) (see REPL)
  • Automatic and type-safe selection of object/array sub tree stores
  • Absolute and relative path access to state items

Usage

immerStore

Syntax:

store = immerStore(value: any);
store = immerStore(value: any, start: (set: (value: any) => void) => () => void);
store = immerStore(value: any, start: (set: (value: any) => void) => () => void, record: (change: { undo?: () => void; redo?: () => void; }) => void);

Function that creates a store containing immutable state. The resulting store implements the Writable contract as well as several additional properties. Specifically, the store contains set, update and select methods as well as a path array.

set is a method that takes one argument which is the value to be set. The store value gets set to the value of the argument if the store value is not already equal to it.

update is a method that takes one argument which is a callback. The callback takes the existing store value as its argument and returns the new value to be set to the store.

select is a method that takes a property, absolute path, relative path or selector. The result is a new store which is linked to the specified subtree of the original store. This store has all the same methods as it's parent store, but with the addition of a delete method which can be used to remove the specified subtree from the original store.

path is an array of string | number | symbol objects specifying the absolute path of the store/sub-store

If a function is passed as the second argument, it will be called when the number of subscribers goes from zero to one (but not from one to two, etc). That function will be passed a set function which changes the value of the store. It must return a stop function that is called when the subscriber count goes from one to zero.

History

const history = new History();

The history class provides a way to track change history and includes the following members:

  • index$ is a readable store containing the current index into the change history.
  • count$ is a readable store containing the current number of changes in the change history.
  • canUndo$ is a readable store containing a boolean indicating if an undo operation can currently be performed.
  • canRedo$ is a readable store containing a boolean indicating if a redo operation can currently be performed.
  • enqueue is a function which can be passed to an immerStore as the third argument allowing easy tracking of change history.

index, count, canUndo, canRedo are also provided as properties which resolve to the values contained in the above stores (uses get internally)

Examples

Basic usage

import { immerStore } from 'svelte-immer-store';

const count = immerStore(0);

count.subscribe(value => {
    console.log(value);
}); // logs '0'

count.set(1); // logs '1'

count.update(n => n + 1); // logs '2'

Making use of immutability

see REPL

Recording Change History

see also REPL

import { immerStore, History } from 'svelte-immer-stor';

const noop = () => {}
const history = new History();
const count = immerStore(0, noop, history.enqueue);

count.subscribe(value => {
    console.log(value);
}); // logs '0'

count.set(1); // logs '1'

count.update(n => n + 1); // logs '2'

history.undo(); // logs '1'

history.undo(); // logs '0'

history.redo(); // logs '1'

Selecting store sub tree

import { immerStore, History } from 'svelte-immer-store';

const root = immerStore({count: 1, object: {value: 2}});

const count = root.select(root => root.count);
const object = root.select(root => root.object);

// each of these is equivalent
//const value = object.select(['value'], 0); // relative path
//const value = object.select(['object', 'value']); // absolute path
//const value = object.select('value'); // property
const value = object.select(object => object.value); // selector
//const value = root.select(root => root.object.value); // selector

object.subscribe(object => {
    console.log(object);
}); // logs '{ value: 2 }'

count.set(2); // does not log anything

value.set(3); // logs '{ value: 3 }'