Lines Matching full:scripts

2 title: scripts
4 description: How npm handles the "scripts" field
9 The `"scripts"` property of your `package.json` file supports a number
10 of built-in scripts and their preset life cycle events as well as
11 arbitrary scripts. These all can be executed by running
14 `myscript`, `postmyscript`). Scripts from dependencies can be run with
17 ### Pre & Post Scripts
19 To create "pre" or "post" scripts for any scripts defined in the
20 `"scripts"` section of the `package.json`, simply create another script
25   "scripts": {
33 In this example `npm run compress` would execute these scripts as
36 ### Life Cycle Scripts
38 There are some special life cycle scripts that happen only in certain
39 situations. These scripts happen in addition to the `pre<event>`, `post<event>`, and
40 `<event>` scripts.
55 * As of `npm@7` these scripts run in the background.
56   To see the output, run with: `--foreground-scripts`.
141 haven't defined your own `install` or `preinstall` scripts, npm will
145 These are run from the scripts of `<pkg-name>`
216 #### A Note on a lack of [`npm uninstall`](/commands/npm-uninstall) scripts
218 While npm v6 had `uninstall` lifecycle scripts, npm v7 does not. Removal of a package can happen fo…
228 Due to the lack of necessary context, `uninstall` lifecycle scripts are not implemented and will no…
232 When npm is run as root, scripts are always run with the effective uid
237 Package scripts run in an environment where many pieces of information
243 If you depend on modules that define executable scripts, like test
245 executing the scripts.  So, if your package.json has this:
253   "scripts": {
266 package.json file, then your package scripts would have the
282 `{"scripts":{"install":"foo.js"}}` in your package.json, then you'd
295   "scripts" : {
296     "install" : "scripts/install.js",
297     "postinstall" : "scripts/install.js"
302 then `scripts/install.js` will be called for the install and post-install
303 stages of the lifecycle.  Since `scripts/install.js` is running for two
312   "scripts" : {
322 Scripts are run by passing the line as a script argument to `sh`.
336 * Try not to use scripts to do what npm can do for you.  Read through
351   scripts is for compilation which must be done on the target architecture.
352 * Scripts are run from the root of the package folder, regardless of what the