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

@ceski23/stan-js-utils

v1.0.0

Published

This package is UNOFFICIAL set of utils for use with [stan-js](https://github.com/codemask-labs/stan-js).

Downloads

4

Readme

stan-js utils

This package is UNOFFICIAL set of utils for use with stan-js.

withMigrations

This is small util that helps to maintain backward compatibility of state when persisting it e.g. in localStorage. It accepts one parameter - configuration object with few params:

  • version - this is current version of your state, you should increase it each time you change your state in non-backwards compatible way
  • migrations - object with state migrations, each key is version number and value is function which will get old state and should return migrated state
  • serialize/deserialize - custom (de)serializer, same as in stan-js

Small example

Let's say you stored user info in store and persisted it in localStorage:

type UserData = {
    username: string
}

const store = createStore({
  user: storage<UserData | null>(null, {
    ...withMigrations({
      version: 0,
      migrations: {},
    }),
  }),
})

Then, after some time you decide that you also want to have user's name in that state. You now have to do two steps:

  1. increase state's version
  2. add migration to new shape
const userDataV0Schema = z.object({
  username: z.string(),
})

type UserData = {
  username: string
  name: string
}

const store = createStore({
  user: storage<UserData | null>(null, {
    ...withMigrations({
      version: 1,
      migrations: {
        1: (prev: unknown) => {
          const { success, data } = userDataV0Schema.safeParse(prev)
		      return success ? { ...data, name: data.username } : null
		    },
	    },
	  }),
  }),
})

In above example we declare migration from version 0 to 1 which is using zod to parse data and add new property. In the future if you change state's shape again you will have to repeat those steps.

Let's add age property:

const userDataV0Schema = z.object({
  username: z.string(),
})

const userDataV1Schema = userDataV0Schema.extend({
  name: z.string(),
})

type UserData = {
  username: string
  name: string
}

const store = createStore({
  user: storage<UserData | null>(null, {
    ...withMigrations({
      version: 2,
      migrations: {
        1: (prev: unknown) => {
          const { success, data } = userDataV0Schema.safeParse(prev)
          return success ? { ...data, name: data.username } : null
        },
        2: (prev: unknown) => {
          const { success, data } = userDataV1Schema.safeParse(prev)
          return success ? { ...data, age: 0 } : null
        },
      },
    }),
  }),
})