diff options
| author | Ruy Adorno <ruyadorno@hotmail.com> | 2021-03-05 01:10:55 +0300 |
|---|---|---|
| committer | Ruy Adorno <ruyadorno@hotmail.com> | 2021-03-05 01:10:55 +0300 |
| commit | 8806015fdd025f73ccf4001472370eafd3c5a856 (patch) | |
| tree | f22d23d6d5528ff5c38e9a7cfe81195f8cfa5ed2 /docs | |
| parent | 323aeceb644963cbbc3034ab0502b713fb36b5d6 (diff) | |
fix: markdown error on using-npm/scripts docsrelease/v7.6.1
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/content/using-npm/scripts.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/content/using-npm/scripts.md b/docs/content/using-npm/scripts.md index 00ef822bf..9312a2154 100644 --- a/docs/content/using-npm/scripts.md +++ b/docs/content/using-npm/scripts.md @@ -8,9 +8,9 @@ description: How npm handles the "scripts" field The `"scripts"` property of your `package.json` file supports a number of built-in scripts and their preset life cycle events as well as -arbitrary scripts. These all can be executed by running `npm run-script -<stage>` or `npm run <stage>` for short. *Pre* and *post* commands with -matching names will be run for those as well (e.g. `premyscript`, +arbitrary scripts. These all can be executed by running +`npm run-script <stage>` or `npm run <stage>` for short. *Pre* and *post* +commands with matching names will be run for those as well (e.g. `premyscript`, `myscript`, `postmyscript`). Scripts from dependencies can be run with `npm explore <pkg> -- npm run <stage>`. |