Lines Matching refs:scripts

3 title: scripts
4 description: How npm handles the "scripts" field
7 # scripts(7)
9 ## How npm handles the "scripts" field
13 …"scripts"` property of of your `package.json` file supports a number of built-in scripts and their…
17 To create "pre" or "post" scripts for any scripts defined in the `"scripts"` section of the `packag…
21   "scripts": {
31 There are some special life cycle scripts that happen only in certain situations. These scripts hap…
124   haven't defined your own `install` or `preinstall` scripts, npm will
131 defaults to `nobody`.  Set the `unsafe-perm` flag to run scripts with
136 Package scripts run in an environment where many pieces of information
143 If you depend on modules that define executable scripts, like test
145 executing the scripts.  So, if your package.json has this:
153   "scripts": { 
166 package.json file, then your package scripts would have the
190   "scripts" : { 
216 `{"scripts":{"install":"foo.js"}}` in your package.json, then you'd
229   "scripts" : { 
230     "install" : "scripts/install.js", 
231     "postinstall" : "scripts/install.js", 
232     "uninstall" : "scripts/uninstall.js"
237 then `scripts/install.js` will be called for the install
238 and post-install stages of the lifecycle, and `scripts/uninstall.js`
240 `scripts/install.js` is running for two different phases, it would
249   "scripts" : { 
277 Hook scripts are run exactly the same way as package.json scripts.
284   Except for uninstall scripts, this will cause the npm action to
288 * Try not to use scripts to do what npm can do for you.  Read through
303   scripts is for compilation which must be done on the target architecture.