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

termigrator-cli

v0.4.0

Published

cli for termigrator

Downloads

3

Readme

termigrator-cli

a CLI tool (using yargs) for termigrator migration apps.

Installing

npm install --save termigrator termigrator-cli

Getting Started

  • create a cli
// in ./lib/cli
import Cli from 'termigrator-cli'

import migrator from './path/to/migrator'
import pkg from '../package.json'

export default new Cli({
  version: pkg.version,
  migrator,
})
  • create bin file in ./bin/your-app-name
#!/usr/local/env node

require('../dist/cli').start()
  • update the file permissions to make it executable
chmod +x ./bin/your-app-name
  • add npm bin entry to package.json
{
  "bin": "./bin/your-app-name"
}

Configuration

Both the CLI and migrator can be configured using the configure and createMigrator hooks.

import Cli from 'termigrator-cli'

import createMigrator from './path/to/migrator'
import pkg from '../package.json'

export default new Cli({
  version: pkg.version,

  // define a #configure method that receives the yargs instance
  configure(yargs) {
    return yargs.options({
      foo: {
        alias: 'f',
        describe: 'my custom global option',
        demand: true,
        global: true,
        default: 'bar'
      }
    })
  },

  // define a #createMigrator method (instead of passing in the migrator) that
  // receives the parsed argv instance from yargs and should return a valid
  // migrator or a promise that resolves to a valid migrator
  createMigrator(argv) {
    return createMigrator(argv.foo)
  }
})

CLI

Basic usage

$ your-app-name --help

current

$ your-app-name current

List the last executed migration


down

$ your-app-name down <version>

Run migrations in the down direction

Options

| name | description | | --- | --- | | -t, --to | the exclusive lower limit on the migrations to execute |


exec

$ your-app-name exec <version> <direction>

Execute a single migration method

Options

| name | description | | --- | --- | | -s, --silent | skip logging of migration events |


goto

$ your-app-name goto <version>

go from the current state to the specified state (in either direction)


pending

$ your-app-name pending

List all pending migrations for the current environment


up

$ your-app-name up [version]

Run pending migrations in the up direction

Options

| name | description | | --- | --- | | -t, --to | the inclusive upper limit on the migrations to execute |


Testing

run the test suite

npm test

run coverage

npm run coverage

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

License

Copyright (c) 2016 Chris Ludden. Licensed under the MIT license.