Gecko [ unitednationsplay.com ]

Linux unitednationsplay.com 3.10.0-1160.45.1.el7.x86_64 #1 SMP Wed Oct 13 17:20:51 UTC 2021 x86_64
nginx/1.20.1
Server IP : 188.130.139.92 & Your IP : 3.134.253.166
Domains : Cant Read [ /etc/named.conf ]
User : web

Name	Size	Permission	Date
test	[ DIR ]	drwxr-xr-x	2021-02-04 21:24
.npmignore	609 B	-rw-r--r--	2015-01-13 02:54
LICENSE	752 B	-rw-r--r--	2015-01-13 04:10
README.md	1.1 KB	-rw-r--r--	2015-07-07 19:00
README.md~	1.03 KB	-rw-r--r--	2015-01-13 04:20
in-install.js	115 B	-rwxr-xr-x	2015-07-07 18:49
in-publish.js	115 B	-rwxr-xr-x	2015-07-07 18:49
index.js	666 B	-rw-r--r--	2015-07-07 18:52
not-in-install.js	115 B	-rwxr-xr-x	2015-07-07 18:54
not-in-publish.js	115 B	-rwxr-xr-x	2015-07-07 18:54
package.json	1.3 KB	-rw-r--r--	2021-02-04 21:24

Rename

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:

```json
  "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:

```json
  "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`.