From 8806015fdd025f73ccf4001472370eafd3c5a856 Mon Sep 17 00:00:00 2001 From: Ruy Adorno Date: Thu, 4 Mar 2021 17:10:55 -0500 Subject: [PATCH] fix: markdown error on using-npm/scripts docs --- docs/content/using-npm/scripts.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/content/using-npm/scripts.md b/docs/content/using-npm/scripts.md index 00ef822bf9001..9312a21546d6f 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 -` or `npm run ` 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 ` or `npm run ` 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 -- npm run `.