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

docs(package-lock): Added package-lock resolved example #250

Merged
merged 2 commits into from
Sep 18, 2019
Merged

docs(package-lock): Added package-lock resolved example #250

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
bd4c86e
docs(package-lock): Added package-lock resolved ex
ruyadorno Sep 13, 2019
a096eb7
Better wording on examples steps
ruyadorno Sep 13, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions doc/spec/package-lock.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,24 @@ this resource.
URL. If the tarball URL isn't on the same server as the registry URL then
this is a complete URL.

eg, Given a `package-lock.json` file containing:

```
"resolved": "https://registry.npmjs.org/example/-/example-1.0.0.tgz"
```

and a registry source configuring a custom value:

```
npm install --registry https://registry.example.com
```

the package will be fetched from the custom-defined registry:

```
https://registry.example.com/example/-/example-1.0.0.tgz
```

#### link *(new)*

If this module was symlinked in development but had semver in the
Expand Down