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

@wedgekit/migrations

v1.6.0

Published

A CLI to painlessly™ migrate previous versions of metadata to the current version.

Downloads

30

Readme

@wedgekit/migrations

A CLI to painlessly™ migrate previous versions of metadata to the current version.

@wedgekit/migrations

Getting Started

In order to keep your migrations ever-green, we recommend only ever running @wedgekit/migrations via npx:

npx @wedgekit/migrations 0.4.0 ./settings.json

Usage

Description
  A CLI to painlessly™ migrate previous versions of metadata to the current version.

Usage
  $ @wedgekit/migrations <version> <src> [options]

Options
  -o, --output     Output file destination. This can be a directory or a file.
  -v, --version    Displays current version
  -h, --help       Displays this message

Examples
  $ @wedgekit/migrations 0.4.1 ./settings.json -o ./settings.new.json
  $ @wedgekit/migrations 0.4.2 params-bt.json params-rt.json

API

@wedgekit/migrations <version> <src> [options]

version

Type: string

Required: ✅

A qualified semver version without a v prefix describing the version of the metadata document being migrated. @wedgekit/migrations will always take documents to the current version of this package, which should always be in sync with the latest version of the metadata specification.

src

Type: string

Required: ✅

The source metadata document which you wish to migrate to a new version of the metadata spec.

This may be a single document or multiple.

options.output

Type: string

Alias: -o

Required: ❌

Default: <src>

The destination directory or file to write the migrated document to. If output is a directory, the filename will be settings.json and it WILL NOT check for an overwrite.

If you are including multiple sources, options.output MUST be a directory or left blank.

If excluded, @wedgekit/migrations will write back to the source document.