Skip to content

Commit 52d32d1

Browse files
dr-jsdarcyclarke
authored andcommitted
docs: match npm-exec.md -p usage with lib/exec.js
updated usage from: https://github.com/npm/cli/blob/v7.0.1/lib/exec.js#L8-L20, and removed extra `-p` occurrences to avoid confusion. Credit: @dr-js Close: #1970 Reviewed-by: @ruyadorno
1 parent 052e977 commit 52d32d1

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/content/commands/npm-exec.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -30,9 +30,9 @@ This command allows you to run an arbitrary command from an npm package
3030
(either one installed locally, or fetched remotely), in a similar context
3131
as running it via `npm run`.
3232

33-
Whatever packages are specified by the `--package` or `-p` option will be
33+
Whatever packages are specified by the `--package` option will be
3434
provided in the `PATH` of the executed command, along with any locally
35-
installed package executables. The `--package` or `-p` option may be
35+
installed package executables. The `--package` option may be
3636
specified multiple times, to execute the supplied command in an environment
3737
where all specified packages are available.
3838

@@ -48,7 +48,7 @@ only be considered a match if they have the exact same name and version as
4848
the local dependency.
4949

5050
If no `-c` or `--call` option is provided, then the positional arguments
51-
are used to generate the command string. If no `-p` or `--package` options
51+
are used to generate the command string. If no `--package` options
5252
are provided, then npm will attempt to determine the executable name from
5353
the package specifier provided as the first positional argument according
5454
to the following heuristic:

0 commit comments

Comments
 (0)