Skip to content

Commit 9cc141d

Browse files
authored
fix(doc): instances of calling the tool should be consistent. (#38)
* This makes sure that all mentions of how to call this module are consistent. * Updates instances of `npx support ...` to `npx @pkgjs/support`
1 parent d7f08f0 commit 9cc141d

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

doc/command-line-usage.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ case.
1212
Once you have node.js installed (version 10.x or later) you can
1313
run the support command directly using npx or optionally npm install the
1414
package and add the `bin` directory to your path. In either case
15-
you can run the support tool using `npx support`.
15+
you can run the support tool using `npx @pkgjs/support`.
1616

1717
## Package Consumers
1818

@@ -35,7 +35,7 @@ The general flow is:
3535

3636
* install the package to display package support information for
3737
* cd into the directory which contains the root package
38-
* execute `npx support show`
38+
* execute `npx @pkgjs/support show`
3939

4040
For example once node.js and the package support tool are installed to show
4141
the package support for a module (the support module itself in this example):
@@ -181,7 +181,7 @@ and the file containing the support info (package-support.json by default) is va
181181
explains the options for providing support info and what goes into the package.json for
182182
each case.
183183
184-
`npx support validate` is run from the directory that contains the package.json for the package.
184+
`npx @pkgjs/support validate` is run from the directory that contains the package.json for the package.
185185
Depending the how the `support` section in the package.json is configured validate will:
186186
187187
* validate the format of the `support` section in the package.json conforms to the

0 commit comments

Comments
 (0)