RetroSearch Browse

Showing content from https://github.com/npm/cli/commit/746ac5d95dc19a74c519a8e3f3e1eed029957921 below:

File tree Expand file treeCollapse file tree 1 file changed

-1

lines changed

Filter options

Expand file treeCollapse file tree 1 file changed

-1

lines changed Original file line number Diff line number Diff line change


 @@ -9,7 +9,7 @@ description: How npm handles the "scripts" field

9 9


 The `"scripts"` property of your `package.json` file supports a number

10 10


 of built-in scripts and their preset life cycle events as well as

11 11


 arbitrary scripts. These all can be executed by running

12

-
 `npm run <stage>` or `npm run <stage>` for short. *Pre* and *post*

12

+
 `npm run <stage>`. *Pre* and *post*

13 13


 commands with matching names will be run for those as well (e.g. `premyscript`,

14 14


 `myscript`, `postmyscript`). Scripts from dependencies can be run with

15 15


 `npm explore <pkg> -- npm run <stage>`.

You can’t perform that action at this time.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4