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

semgrator

v0.3.0

Published

Run migrations code based on semantic version rules

Downloads

554,121

Readme

semgrator

semgrator provides an utility to support backward compatibility when building frameworks and runtimes that do not introduce breaking changes via new options.

What is a compatibility option/flag/mode?

If you want to create a product that is configurable, but you do not want to break your users on behavior changes, you can introduce a new option that turns on and off the new behavior, and turn the new behavior by default. Users of the previous behavior would be required to change their configuration to keep using the software.

How semgrator helps

semgrator run migrations code based on semantic version rules. So on a breaking/behavior change that results in a new compatibility option in your configuration file, you can add a new migration rule that set the new option to false automatically.

Install

npm i semgrator

Usage

Writing migrations

import type { Migration } from 'semgrator'
import type { Config } from '../your-config-meta.js'

export const migration: Migration<Config> = {
  version: '1.0.0',
  toVersion: '1.42.0',
  up: (input: Config) => {
    // Do something with Config
    return input
  },
}

The version peroperty specifies the minimum version that do not need the change. In other terms, all versions before the specified one will trigger the migration.

The toVersion property will be used by semgrator as the resulting version after the change. This is useful in case you want to have a final version that is higher than version.

Running semgrator

import { semgrator } from 'semgrator'

type MyConfig = {
  result: unknown
}

const res = await semgrator<MyConfig, MyConfig>({
  version: '1.0.0',
  path: 'path/to/migrations',
  input: {
    result: { foo: 'bar' } as unknown,
  },
})

console.log(res.result)
console.log(res.changed)
console.log(res.version)

Getting intermediate results

import { semgrator } from 'semgrator'

type MyConfig = {
  result: unknown
}

const iterator = semgrator<MyConfig, MyConfig>({
  version: '1.0.0',
  path: 'path/to/migrations',
  input: {
    result: { foo: 'bar' } as unknown,
  },
})

for await (const res of iterator) {
  console.log(res.version, res.result)
}

License

Apache-2.0