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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@quantajs/svelte

v3.0.0

Published

Svelte bindings for QuantaJS stores.

Readme

@quantajs/svelte

CI npm

Svelte bindings for @quantajs/core. QuantaJS stores as Svelte stores, for Svelte 4 and 5 and SvelteKit.

Documentation · Example app · Changelog

Install

npm install @quantajs/core @quantajs/svelte

Usage

// lib/stores/todos.ts
import { defineStore } from '@quantajs/core';

export const useTodoStore = defineStore('todos', {
    state: () => ({ items: [] as { text: string; done: boolean }[] }),
    getters: {
        remaining: (s) => s.items.filter((t) => !t.done).length,
    },
    actions: {
        add(text: string) {
            this.items.push({ text, done: false });
        },
    },
});
<!-- Todos.svelte -->
<script lang="ts">
    import { useQuanta, useQuantaActions, useQuantaValue } from '@quantajs/svelte';
    import { useTodoStore } from '$lib/stores/todos';

    // Notifies only when `remaining` changes.
    const remaining = useQuantaValue(useTodoStore, (s) => s.remaining);

    // The store, without subscribing: for calling actions.
    const actions = useQuantaActions(useTodoStore);

    // Notifies on any change to the store.
    const todos = useQuanta(useTodoStore);
</script>

<p>{$remaining} left</p>
<button onclick={() => actions.add('New todo')}>Add</button>
<ul>
    {#each $todos.items as t}
        <li>{t.text}</li>
    {/each}
</ul>

Each function returns a standard Svelte store, so $ subscriptions work in components, and fromStore from svelte/store turns one into state in a .svelte.ts file. Subscriptions end when the component is destroyed, and a store tracks QuantaJS state only while something is subscribed.

No setup is needed in a client-only app: stores resolve against the default container.

| Function | Notifies on | Use for | | ------------------------------------------------ | ----------------------- | ----------------------------------------------------------- | | useQuantaValue(definition, selector, options?) | What the selector reads | Most components | | useQuanta(definition) | Any change to the store | Small stores, or components that read most of it | | useQuantaActions(definition) | Nothing | Components that only call actions; returns the store itself | | useLocalStore(definition) | Any change to the store | A store instance owned by one component, disposed with it |

A selector that builds a new object or array on every run should pass shallow, so an unchanged projection does not notify:

import { shallow, useQuantaValue } from '@quantajs/svelte';
import { useTodoStore } from '$lib/stores/todos';

export const summary = useQuantaValue(
    useTodoStore,
    (s) => ({ remaining: s.remaining, total: s.items.length }),
    { equalityFn: shallow },
);

SvelteKit and server rendering

Call setQuantaContainer() in the root layout. On the server the layout renders once per request, so each request gets its own container; it is disposed when the layout is destroyed.

<!-- src/routes/+layout.svelte -->
<script lang="ts">
    import { setQuantaContainer } from '@quantajs/svelte';

    let { data, children } = $props();
    setQuantaContainer(undefined, { snapshot: data.snapshot });
</script>

{@render children()}

To load state on the server, resolve stores against a container in a load function and return its snapshot. The layout applies it before anything renders, so the client's markup matches the server's:

// src/routes/+layout.server.ts
import { createContainer } from '@quantajs/core';
import { useTodoStore } from '$lib/stores/todos';

export async function load() {
    const container = createContainer();
    useTodoStore(container).add('Loaded on the server');
    const snapshot = container.dehydrate();
    container.dispose();
    return { snapshot };
}

Never resolve stores against the default container on the server: it is shared by every request. Pass your own container to setQuantaContainer(container) to manage its lifetime yourself.

DevTools

npm install -D @quantajs/devtools
import { enableDevTools } from '@quantajs/svelte';

if (import.meta.env.DEV) {
    enableDevTools({ redact: ['token'] });
    import('@quantajs/devtools').then(({ mountDevTools }) => mountDevTools());
}

License

MIT