Lines Matching +full:before +full:- +full:script

3 \fBscripts\fR - How npm handles the "scripts" field
6 …-in scripts and their preset life cycle events as well as arbitrary scripts. These all can be exec…
9 …\fB"scripts"\fR section of the \fBpackage.json\fR, simply create another script \fIwith a matching…
15     "precompress": "{{ executes BEFORE the `compress` script }}",
17     "postcompress": "{{ executes AFTER `compress` script }}"
36 Runs BEFORE the package is packed, i.e. during \fBnpm publish\fR and \fBnpm pack\fR
40 Runs AFTER \fBprepublish\fR, but BEFORE \fBprepublishOnly\fR
42 … a \fBprepare\fR script, its \fBdependencies\fR and \fBdevDependencies\fR will be installed, and t…
44 …@7\fR these scripts run in the background. To see the output, run with: \fB--foreground-scripts\fR.
58 Runs BEFORE the package is prepared and packed, ONLY on \fBnpm publish\fR.
65 Runs BEFORE a tarball is packed (on "\fBnpm pack\fR", "\fBnpm publish\fR", and when installing a gi…
67 …e as "\fBnpm pack\fR". "\fBnpm run pack\fR" is an arbitrary user defined script name, where as, "\…
74 Runs AFTER the tarball has been generated but before it is moved to its final destination (if at al…
90 Since \fBnpm@1.1.71\fR, the npm CLI has run the \fBprepublish\fR script for both \fBnpm publish\fR …
96 …ckage before it is used, in a way that is not dependent on the operating system or architecture of…
110 You can depend on \fBcoffee-script\fR as a \fBdevDependency\fR, and thus your users don't need to h…
119 …script is run any time an \fBnpm\fR command causes changes to the \fBnode_modules\fR directory. It…
155 These also run when you run \fBnpm install -g <pkg-name>\fR
174 …ll\fR scripts, npm will default the \fBinstall\fR command to compile using node-gyp via \fBnode-gyp
177 These are run from the scripts of \fB<pkg-name>\fR
220 If there is a \fBrestart\fR script defined, these events are run, otherwise \fBstop\fR and \fBstart…
230 .SS "\fB\fBnpm run <user defined>\fR\fR \fI\(la/commands/npm-run-script\(ra\fR"
233 \fBpre<user-defined>\fR
235 \fB<user-defined>\fR
237 \fBpost<user-defined>\fR
284 … wide variety of reasons, and there's no clear way to currently give the script enough context to …
326 then you could run \fBnpm start\fR to execute the \fBbar\fR script, which is exported into the \fBn…
331 See \fB\fBpackage.json\fR\fR \fI\(la/configuring-npm/package-json\(ra\fR for more on package config…
334 …chever stage of the cycle is being executed. So, you could have a single script used for different…
336 …had \fB{"scripts":{"install":"foo.js"}}\fR in your package.json, then you'd see this in the script:
358 then \fBscripts/install.js\fR will be called for the install and post-install stages of the lifecyc…
375 Scripts are run by passing the line as a script argument to \fBsh\fR.
377 If the script exits with a code other than 0, then this will abort the process.
379 Note that these script files don't have to be Node.js or even JavaScript programs. They just have t…
383 Don't exit with a non-zero error code unless you \fIreally\fR mean it. If the failure is minor or o…
385 … do for you. Read through \fB\fBpackage.json\fR\fR \fI\(la/configuring-npm/package-json\(ra\fR to …
389 Don't prefix your script commands with "sudo". If root permissions are required for some reason, th…
391 …. You should almost never have to explicitly set a preinstall or install script. If you are doing …
393 …current working directory is when \fBnpm\fR is invoked. If you want your script to use different b…
399 npm help run-script
401 \fBpackage.json\fR \fI\(la/configuring-npm/package-json\(ra\fR