in-publish
    Overview
    Documentation
    Tutorials
    Insights
    Code
    Dependencies
    Contributors
    Jobs

in-publish

Detect if we were run as a result of `npm publish`

2.0.0  •  Updated 3 years ago  •  by Rebecca Turner  •  ISC License

in-publish

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 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 examplea 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.

Popularity

Weekly Downloads
3.4M
Stars
110

Maintenance

Development

Last ver 5 years ago
Created 5 years ago
Last commit 3 years ago
2 months between commits

Technology

Node version: 2.3.3
0 unpacked

Compliance

ISC License
OSI Approved
0 vulnerabilities

Contributors

3 contributors
Rebecca Turner
Maintainer, 11 commits, 2 merges
Works at Oncue
Lewis Cowper
1 commits, 1 PRs
Shahar Or
1 commits, 1 PRs
igorklopov
1 PRs
garthk
1 PRs

Dependencies

Openbase helps developers choose among and use millions of open-source packages, so they can build amazing products faster.
FacebookTwitterLinkedIn
© 2020 Devstore, Inc.