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 🙏

© 2025 – Pkg Stats / Ryan Hefner

svelte-result-store

v1.1.0

Published

Svelte store with error handling and propagation

Readme

svelte-result-store

Svelte store that does error handling and promises.

Introduction

Svelte stores are great but becomes cumbersome to use when you need error handling and want to compose a flow of multiple, possibly failing stores.

svelte-result-store introduces a new concept on top of the standard svelte/store that is the Result<T> = {value?: T; error?: Error} type. A Result can have three states, either unresolved (no error, no value), resolved with value or resolved with error.

This module exports the same three methods as svelte/store, ({readable, writable, derived}) and they work mostly the same but on Results. A notable difference is that svelte-result-store does not require an initial value and considers undefined to be "unresolved" instead of an actual value (use null if you need to work with optional values).

With this we can let the derived stores act only on resolved values and short-circuit a chain of derived stores if an error occurs - not requiring you to check for errors at each step - for example:

const numberStore = writable() // no initial value required

HorseSensor.global.addEventListener('neeeeigh', (event) => {
    numberStore.set({value: event.hay.numNeedles})
})

const remoteStore = readable((set, error) => {
    fetch('https://example.com').then((res) => res.json()).then(set).catch(error)
})

const derivedStore = derived([numberStore, remoteStore], ([number, data] => {
    // number and data is guaranteed to be available here
    return number * data.stonks
}))

derivedStore.subscribe((result) => {
    if (result.error) {
        console.log(error)
    } else if (result.value) {
        console.log(result.value)
    } else {
        console.log('pending')
    }
})

And since the result stores work nicely with promises you could write the remoteStore from above using an async function instead:

const remoteStore = readable(async () => {
    const res = await fetch('https://example.com')
    return res.json()
})

In fact any function passed to readable, writable or derived can be async and errors thrown (both async and sync) will propagate to the Result.

The readable stores returned by this library also expose some convenience getters, for example if we are only interested in the resulting values from the above example we could do:

derivedStore.value.subscribe((value) => console.log('haystocks signal', value))

Or even better (since you would never dream of just ignoring an error, right?):

derivedStore
    .catch((error) => console.log('Unexpected error!', error))
    .subscribe((value) => console.log('haystocks signal', value))

See the source or generated type definitions for a list of all helper methods :)

Installation

The svelte-result-store package is distributed as a module on npm.

yarn add svelte-result-store
# or
npm install --save svelte-result-store

Example usage

import {readable, derived} from 'svelte-result-store'

const things = readable(async () => {
    const data = await getData()
    if (data.badThings) {
        throw new Error('Bad things')
    }
    return data.things
})

const otherThings = readable((set) => {
    set(42)
})

const allThings = derived([things, otherThings], async ([$things, $otherThings]) => {
    const result = await computeAllThings($things, $otherThings)
    return result.all
})

allThings.value.subscribe((value) => {
    if (value) {
        console.log('GOT ALL THE THINGS', value)
    }
})

allThings.error.subscribe((error) => {
    if (error) {
        console.log('Things are bad', error)
    }
})

Developing

You need Make, node.js and yarn installed.

Clone the repository and run make to checkout all dependencies and build the project. See the Makefile for other useful targets. Before submitting a pull request make sure to run make lint.


Made with ☕️ & ❤️ by Greymass, if you find this useful please consider supporting us.