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-xstate

v1.0.1

Published

Provides a simple function much like the @xstate/react to simplify usage of xstate machines with Svelte

Readme

svelte-xstate

Installation

npm i --save-dev svelte-xstate

Usage

Assuming you have an xstate machine defined at ../machines/machine

<script>
    import machine from '../machines/myMachine'
    import { useMachine } from 'svelte-xstate'

    let [state, send] = useMachine(machine.withConfig({}, { todos: [] }))

    let todos
    $: todos = $state.context.todos

    let addTodo = todo => {
        send('ADD_TODO', todo)
    }
</script>

<div>
    Current state : {$state.value}
</div>

{#if $state.matches('LOADING')}
    <span>Loading...</span>
{/if}

state is a svelte store so you need to use $state when accessing it send is simply the service.send method of the xstate machine

Possible gotcha

It seems there are some problems with Rollup/Svelte/xstate because of the process variable not being defined

Hopefully there is a rather easy fix, thanks to RikuVan's config file

You just need to add rollup-plugin-replace

npm i --save-dev rollup-plugin-replace

Then call it in the plugins array, after svelte :

replace({
    "process.env.NODE_ENV": production
        ? JSON.stringify("production")
        : JSON.stringify("development")
}),

According to this xstate issue Svelte should be replacing process as it's a convention.