Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: fix typo in file-specifiers and package-lock #16

Merged
merged 2 commits into from
Jul 18, 2018
Merged

docs: fix typo in file-specifiers and package-lock #16

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
16de1c5
docs: fix typo in doc/spec/file-specifiers.md
watilde Jul 18, 2018
ce09b89
docs: fix typo in doc/spec/package-lock.md
watilde Jul 18, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/spec/file-specifiers.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already fixed at #15

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
Expand Down Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion doc/spec/package-lock.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down