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

counsel-script

v0.4.1

Published

adds a npm script to package.json

Downloads

70

Readme

counsel-script

adds a npm/yarn script to package.json.

example

  • create your rules
const ScriptRule = require('counsel-script')
let publishRules = [
  new ScriptRule({
    scriptName: 'publish-minor', // required
    scriptCommand: 'npm version minor', // required
    scriptAppend: true
  })
  new ScriptRule({
    scriptName: 'publish-minor',
    scriptCommand: 'git push origin master --tags && npm publish',

    // optional, let multiple ScriptRules add to the same `script`.
    // see the result below to understand how these two `publish-minor` scripts
    // are combined.
    scriptAppend: true
  })
  new ScriptRule({
    scriptName: 'bananas',
    scriptCommand: 'bananas --peel',
    // permit variants of a script to exist for `scriptName`.
    // variants can be explict strings or RegExp's
    // @NOTE: `scriptCommandVariants: '*'` allows any user provided script to override the rule
    scriptCommandVariants: [
      'bananas --eat',
      'apples --eat',
      /fruit.io --consume/
    ],
  })
]
...
  • apply your rules (per counsel docs)
  • observe your package.json's publish-minor script
{
  "name": "my-package",
  "scripts": {
    "publish-minor": "npm version minor && git push origin master --tags && npm publish",
    "bananas": "bananas --peel"
  },
  ...
}

in this contrived example, we observe how the ScriptRule can add scripts to the package. further, we can see how in append mode, you can chain commands to a common script name.