diff options
author | Mary <Ipadlover8322@gmail.com> | 2018-07-18 05:56:20 +0300 |
---|---|---|
committer | Kat Marchán <kzm@zkat.tech> | 2018-07-18 05:56:20 +0300 |
commit | ca03013c23ff38e12902e9569a61265c2d613738 (patch) | |
tree | c2773b228186eb358a29d317738872ffd4aa7c42 /doc | |
parent | 06580877b6023643ec780c19d84fbe120fe5425c (diff) |
docs: fix some typos in file-specifiers spec (#15)
PR-URL: https://github.com/npm/cli/pull/15
Credit: @Mstrodl
Reviewed-By: @zkat
Diffstat (limited to 'doc')
-rw-r--r-- | doc/spec/file-specifiers.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/spec/file-specifiers.md b/doc/spec/file-specifiers.md index 226f6d013..8e9e73d4d 100644 --- a/doc/spec/file-specifiers.md +++ b/doc/spec/file-specifiers.md @@ -14,7 +14,7 @@ URLs and URL-like strings for other types. slashes on a file specifier will be removed, that is 'file://../foo/bar` references the same package as same as `file:../foo/bar`. The latter is considered canonical. -* Attempting to install a specifer that has a windows drive letter will +* Attempting to install a specifier that has a windows drive letter will produce an error on non-Windows systems. * A valid `file:` specifier points is: * a valid package file. That is, a `.tar`, `.tar.gz` or `.tgz` containing @@ -64,7 +64,7 @@ down the destination package's `node_modules` you should create a shrinkwrap for separately. This is necessary to support the mono repo use case where many projects file -to the same package. If each project included its own npm-shrinkwrap.json +to the same package. If each project included its own `npm-shrinkwrap.json` then they would each have their own distinct set of transitive dependencies and they'd step on each other any time you ran an install in one or the other. @@ -75,7 +75,7 @@ shrinkwrapped packages. #### File type specifiers pointing at tarballs -File-type specifiers pointing at a `.tgz` or `.tar.gz or `.tar` file will +File-type specifiers pointing at a `.tgz` or `.tar.gz` or `.tar` file will install it as a package file in the same way we would a remote tarball. The checksum of the package file should be recorded so that we can check for updates. |