diff options
Diffstat (limited to 'deps/npm/html/doc/files/npm-json.html')
| -rw-r--r-- | deps/npm/html/doc/files/npm-json.html | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/deps/npm/html/doc/files/npm-json.html b/deps/npm/html/doc/files/npm-json.html index 0edcca4702..5d9a0f79b6 100644 --- a/deps/npm/html/doc/files/npm-json.html +++ b/deps/npm/html/doc/files/npm-json.html @@ -81,7 +81,7 @@ current SPDX license identifier for the license you're using, like this:</p> <pre><code>{ "license" : "BSD-3-Clause" }</code></pre><p>You can check <a href="https://spdx.org/licenses/">the full list of SPDX license IDs</a>. Ideally you should pick one that is <a href="https://opensource.org/licenses/alphabetical">OSI</a> approved.</p> -<p>If your package is licensed under multiple common licenses, use an <a href="https://npmjs.com/package/spdx">SPDX license +<p>If your package is licensed under multiple common licenses, use an <a href="https://www.npmjs.com/package/spdx">SPDX license expression syntax version 2.0 string</a>, like this:</p> <pre><code>{ "license" : "(ISC OR GPL-3.0)" }</code></pre><p>If you are using a license that hasn't been assigned an SPDX identifier, or if you are using a custom license, use a string value like this one:</p> @@ -256,15 +256,15 @@ future.</p> want to contribute. If the git repo is on GitHub, then the <code>npm docs</code> command will be able to find you.</p> <p>Do it like this:</p> -<pre><code>"repository" : - { "type" : "git" - , "url" : "https://github.com/npm/cli.git" - } +<pre><code>"repository": { + "type" : "git", + "url" : "https://github.com/npm/cli.git" +} -"repository" : - { "type" : "svn" - , "url" : "https://v8.googlecode.com/svn/trunk/" - }</code></pre><p>The URL should be a publicly available (perhaps read-only) url that can be handed +"repository": { + "type" : "svn", + "url" : "https://v8.googlecode.com/svn/trunk/" +}</code></pre><p>The URL should be a publicly available (perhaps read-only) url that can be handed directly to a VCS program without any modification. It should not be a url to an html project page that you put in your browser. It's for computers.</p> <p>For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same @@ -434,7 +434,7 @@ dependency hell, a situation that npm is designed to avoid as much as possible.< <p>Trying to install another plugin with a conflicting requirement will cause an error. For this reason, make sure your plugin requirement is as broad as possible, and not to lock it down to specific patch versions.</p> -<p>Assuming the host complies with <a href="http://semver.org/">semver</a>, only changes in +<p>Assuming the host complies with <a href="https://semver.org/">semver</a>, only changes in the host package's major version will break your plugin. Thus, if you've worked with every 1.x version of the host package, use <code>"^1.0"</code> or <code>"1.x"</code> to express this. If you depend on features introduced in 1.5.2, use <code>">= 1.5.2 < 2"</code>.</p> @@ -574,5 +574,5 @@ ignored.</p> <tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> <tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> </table> -<p id="footer">package.json — npm@6.2.0</p> +<p id="footer">package.json — npm@6.4.1</p> |