From 16de1c55bbb05b0bb8bd9f1c53b7db14169900c8 Mon Sep 17 00:00:00 2001 From: Daijiro Wachi Date: Wed, 18 Jul 2018 09:57:00 +0900 Subject: [PATCH 1/2] docs: fix typo in doc/spec/file-specifiers.md + specifer => specifiers + relavent => relevant --- doc/spec/file-specifiers.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/spec/file-specifiers.md b/doc/spec/file-specifiers.md index 226f6d0136728..95029677f5f45 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 @@ -134,7 +134,7 @@ example-package@1.0.0 /path/to/example-package +-- a -> file:../a ``` -Of note here: No version is included as the relavent detail is WHERE the +Of note here: No version is included as the relevant detail is WHERE the package came from, not what version happened to be in that path. ### Outdated From ce09b89465c53669fc3b41e45d57ad4175a3ac17 Mon Sep 17 00:00:00 2001 From: Daijiro Wachi Date: Wed, 18 Jul 2018 09:57:40 +0900 Subject: [PATCH 2/2] docs: fix typo in doc/spec/package-lock.md + properities => properties --- doc/spec/package-lock.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/spec/package-lock.md b/doc/spec/package-lock.md index e1cc6941aee3e..9da5d8c03b45a 100644 --- a/doc/spec/package-lock.md +++ b/doc/spec/package-lock.md @@ -269,7 +269,7 @@ nothing requires it any more. ## Additional fields / Adding new fields Installers should ignore any field they aren't aware of. It's not an error -to have additional properities in the package-lock or lock file. +to have additional properties in the package-lock or lock file. Installers that want to add new fields should either have one added via RFC in the npm issue tracker and an accompanying documentation PR, or should prefix