Skip to content

Commit 7e1e841

Browse files
ethomsonwraithgar
authored andcommitted
fix(docs): fix angle brackets in npm diff docs
Emphasizing them like we do everywhere else to fix encoding errors and for consistency. Also removed the `<String>` from the type definition as we don't do that anywhere else. PR-URL: #2662 Credit: @ethomson Close: #2662 Reviewed-by: @wraithgar
1 parent ef687f5 commit 7e1e841

File tree

1 file changed

+6
-6
lines changed

1 file changed

+6
-6
lines changed

docs/content/commands/npm-diff.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -82,11 +82,11 @@ of files for packages published to the npm registry.
8282
When using a single package name (with no version or tag specifier) as an
8383
argument, `npm diff` will work in a similar way to
8484
[`npm-outdated`](npm-outdated) and reach for the registry to figure out
85-
what current published version of the package named <pkg-name> will satisfy
86-
its dependent declared semver-range. Once that specific version is known
87-
`npm diff` will print diff patches comparing the current version of
88-
<pkg-name> found in the local file system with that specific version
89-
returned by the registry.
85+
what current published version of the package named `<pkg-name>`
86+
will satisfy its dependent declared semver-range. Once that specific
87+
version is known `npm diff` will print diff patches comparing the
88+
current version of `<pkg-name>` found in the local file system with
89+
that specific version returned by the registry.
9090
9191
Given a package named `abbrev` that is currently installed:
9292
@@ -155,7 +155,7 @@ located within the folder `./lib/` and changed lines of code within the
155155
156156
#### diff
157157
158-
* Type: Array<String>
158+
* Type: Array
159159
* Default: null
160160
161161
Defines npm package specifiers to compare using the `npm diff` command.

0 commit comments

Comments
 (0)