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

mutent-migration

v0.3.1

Published

Migration plugin for Mutent

Downloads

144

Readme

mutent-migration

npm JavaScript Style Guide

This plugin for Mutent provides an easy way to declare migration strategies for data versioning.

API

mutentMigration(options)

Returns a new Mutent's Plugin that will monitor all fetched Entites and applies the correct migration strategy when needed.

  • options <Object>
  • [options.explicitVersion] <boolean> Do not set the latest version automatically during Entities' creation.
  • [options.forceUpdate] <boolean> Force Entity's update any time is handled.
  • [options.key] <string> Name of the key that holds the Entity's version number.
  • [options.strategies] <Object> Collection of migration functions.
  • options.version <number> The wanted Entity's version.
  • Returns: <Plugin>

Error codes

Those are the error codes (MutentError instances) that can be throwed by this plugin.

EMUT_INVALID_ENTITY_VERSION

The current Entity have an invalid version value.

EMUT_FUTURE_ENTITY

Found an Entity that has a future version.

EMUT_STRATEGY_EXPECTED

An upgrade is required, but the required strategy function is missing.

EMUT_INVALID_UPGRADE

A strategy was applied to an Entity, but the Entity does not contain the expected version.

Example

import { Store } from 'mutent'
import { ArrayAdapter } from 'mutent-array'
import { mutentMigration } from 'mutent-migration'

const items = [
  { id: 1, oldFieldName: 'Calvin' } // implicit "v: 0"
]

const store = new Store({
  adapter: new ArrayAdapter({ items }),
  plugins: [
    mutentMigration({
      // Required version
      version: 1,
      // Version field name
      key: 'v',
      // Migration strategies
      strategies: {
        // Migration strategy from version 0 (or no version) to version 1
        1: ({ oldFieldName, ...data }) => {
          return {
            ...data,
            v: 1,
            newFieldname: oldFieldName
          }
        }
      }
    })
  ]
})

async function foo () {
  // Read and upgrade (in memory)
  const calvin = await store.find(item => item.id === 1).unwrap()
  console.log(calvin) // { id: 1, v: 1, newFieldname: 'Calvin' }

  // Create (set latest version if not defined during creation only)
  const hobbes = await store.create({ id: 2, newFieldname: 'Hobbes' }).unwrap()
  console.log(hobbes) // { id: 2, v: 1, newFieldname: 'Hobbes' }

  // Create from an explicit version
  const prof = await store.create({ id: 3, v: 0, oldFieldName: 'Miss Wormwood' }).unwrap()
  console.log(prof) // { id: 3, v: 1, newFieldname: 'Miss Wormwood' }
}

foo()