in-publish
Detect if we were run as a result of `npm publish`
Last updated 23 days ago by iarna .
ISC · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install in-publish 
SYNC missed versions from official npm registry.

in-publish

For background, see npm#10074.

Detect if we were run as a result of npm publish. This is intended to allow you to easily have prepublish lifecycle scripts that don't run when you run npm install.

$ npm install --save-dev in-publish
in-publish@1.0.0 node_modules/in-publish

Then edit your package.json to have:

  "scripts": {
    "prepublish": "in-publish && thing-I-dont-want-on-dev-install || not-in-publish"
  }

Now when you run:

$ npm install

Then thing-I-dont-want-on-dev-install won't be run, but...

$ npm publish

And thing-I-dont-want-on-dev-install will be run.

It's worth noting that the prepublish lifecycle is ALSO called when you build a tarball, so:

$ npm pack

Will call your prepublish lifecycle, but with the example above, thing-I-dont-want-on-dev-install won't be run.

If you want this, you can use another helper included here:

  "scripts": {
    "prepublish": "not-in-install && thing-I-dont-want-on-dev-install || in-install"
  }

The above will run your thing-I-dont-want-on-dev-install on publish and on pack but not on install.

Current Tags

  • 2.0.1                                ...           latest (23 days ago)

5 Versions

  • 2.0.1                                ...           23 days ago
  • 2.0.0                                ...           5 years ago
  • 1.1.1                                ...           5 years ago
  • 1.1.0                                ...           5 years ago
  • 1.0.0                                ...           5 years ago
Maintainers (1)
Downloads
Today 14,399
This Week 37,614
This Month 96,861
Last Day 16,912
Last Week 93,139
Last Month 351,802
Dependencies (0)
None
Dev Dependencies (0)
None
Dependents (304)

Copyright 2014 - 2016 © taobao.org |