diff options
Diffstat (limited to 'deps/npm/html/doc/json.html')
| -rw-r--r-- | deps/npm/html/doc/json.html | 267 |
1 files changed, 134 insertions, 133 deletions
diff --git a/deps/npm/html/doc/json.html b/deps/npm/html/doc/json.html index 84841e08ae..cdeeaa1fcd 100644 --- a/deps/npm/html/doc/json.html +++ b/deps/npm/html/doc/json.html @@ -6,11 +6,11 @@ <body> <div id="wrapper"> -<h1><a href="../doc/json.html">json</a></h1> <p>Specifics of npm's package.json handling</p> +<h1><a href="../doc/json.html">json</a></h1> <p>Specifics of npm's package.json handling</p> <h2 id="DESCRIPTION">DESCRIPTION</h2> -<p>This document is all you need to know about what's required in your package.json +<p>This document is all you need to know about what's required in your package.json file. It must be actual JSON, not just a JavaScript object literal.</p> <p>A lot of the behavior described in this document is affected by the config @@ -20,9 +20,10 @@ settings described in <code><a href="../doc/config.html">config(1)</a></code>.</ <p>npm will default some values based on package contents.</p> -<ul><li><p><code>"scripts": {"start": "node server.js"}</code></p><p>If there is a <code>server.js</code> file in the root of your package, then npm -will default the <code>start</code> command to <code>node server.js</code>.</p></li><li><p><code>"scripts":{"preinstall": "node-waf clean || true; node-waf configure build"}</code></p><p>If there is a <code>wscript</code> file in the root of your package, npm will -default the <code>preinstall</code> command to compile using node-waf.</p></li><li><p><code>"contributors": [...]</code></p><p>If there is an <code>AUTHORS</code> file in the root of your package, npm will +<ul><li><p><code>"scripts": {"start": "node server.js"}</code></p><p>If there is a <code>server.js</code> file in the root of your package, then npm +will default the <code>start</code> command to <code>node server.js</code>.</p></li><li><p><code>"scripts":{"preinstall": "node-waf clean || true; node-waf configure build"}</code></p><p>If there is a <code>wscript</code> file in the root of your package, npm will +default the <code>preinstall</code> command to compile using node-waf.</p></li><li><p><code>"scripts":{"preinstall": "node-gyp rebuild"}</code></p><p>If there is a <code>binding.gyp</code> file in the root of your package, npm will +default the <code>preinstall</code> command to compile using node-gyp.</p></li><li><p><code>"contributors": [...]</code></p><p>If there is an <code>AUTHORS</code> file in the root of your package, npm will treat each line as a <code>Name <email> (url)</code> format, where email and url are optional. Lines which start with a <code>#</code> or are blank, will be ignored.</p></li></ul> @@ -30,25 +31,25 @@ ignored.</p></li></ul> <h2 id="name">name</h2> <p>The <em>most</em> important things in your package.json are the name and version fields. -Those are actually required, and your package won't install without +Those are actually required, and your package won't install without them. The name and version together form an identifier that is assumed to be completely unique. Changes to the package should come along with changes to the version.</p> <p>The name is what your thing is called. Some tips:</p> -<ul><li>Don't put "js" or "node" in the name. It's assumed that it's js, since you're -writing a package.json file, and you can specify the engine using the "engines" +<ul><li>Don't put "js" or "node" in the name. It's assumed that it's js, since you're +writing a package.json file, and you can specify the engine using the "engines" field. (See below.)</li><li>The name ends up being part of a URL, an argument on the command line, and a folder name. Any name with non-url-safe characters will be rejected. -Also, it can't start with a dot or an underscore.</li><li>The name will probably be passed as an argument to require(), so it should -be something short, but also reasonably descriptive.</li><li>You may want to check the npm registry to see if there's something by that name +Also, it can't start with a dot or an underscore.</li><li>The name will probably be passed as an argument to require(), so it should +be something short, but also reasonably descriptive.</li><li>You may want to check the npm registry to see if there's something by that name already, before you get too attached to it. http://registry.npmjs.org/</li></ul> <h2 id="version">version</h2> <p>The <em>most</em> important things in your package.json are the name and version fields. -Those are actually required, and your package won't install without +Those are actually required, and your package won't install without them. The name and version together form an identifier that is assumed to be completely unique. Changes to the package should come along with changes to the version.</p> @@ -57,89 +58,89 @@ changes to the version.</p> <a href="https://github.com/isaacs/node-semver">node-semver</a>, which is bundled with npm as a dependency. (<code>npm install semver</code> to use it yourself.)</p> -<p>Here's how npm's semver implementation deviates from what's on semver.org:</p> +<p>Here's how npm's semver implementation deviates from what's on semver.org:</p> -<ul><li>Versions can start with "v"</li><li>A numeric item separated from the main three-number version by a hyphen -will be interpreted as a "build" number, and will <em>increase</em> the version. -But, if the tag is not a number separated by a hyphen, then it's treated +<ul><li>Versions can start with "v"</li><li>A numeric item separated from the main three-number version by a hyphen +will be interpreted as a "build" number, and will <em>increase</em> the version. +But, if the tag is not a number separated by a hyphen, then it's treated as a pre-release tag, and is <em>less than</em> the version without a tag. So, <code>0.1.2-7 > 0.1.2-7-beta > 0.1.2-6 > 0.1.2 > 0.1.2beta</code></li></ul> <p>This is a little bit confusing to explain, but matches what you see in practice -when people create tags in git like "v1.2.3" and then do "git describe" to generate +when people create tags in git like "v1.2.3" and then do "git describe" to generate a patch version.</p> <h2 id="description">description</h2> -<p>Put a description in it. It's a string. This helps people discover your -package, as it's listed in <code>npm search</code>.</p> +<p>Put a description in it. It's a string. This helps people discover your +package, as it's listed in <code>npm search</code>.</p> <h2 id="keywords">keywords</h2> -<p>Put keywords in it. It's an array of strings. This helps people -discover your package as it's listed in <code>npm search</code>.</p> +<p>Put keywords in it. It's an array of strings. This helps people +discover your package as it's listed in <code>npm search</code>.</p> <h2 id="homepage">homepage</h2> <p>The url to the project homepage.</p> -<p><strong>NOTE</strong>: This is <em>not</em> the same as "url". If you put a "url" field, -then the registry will think it's a redirection to your package that has +<p><strong>NOTE</strong>: This is <em>not</em> the same as "url". If you put a "url" field, +then the registry will think it's a redirection to your package that has been published somewhere else, and spit at you.</p> -<p>Literally. Spit. I'm so not kidding.</p> +<p>Literally. Spit. I'm so not kidding.</p> <h2 id="bugs">bugs</h2> -<p>The url to your project's issue tracker and / or the email address to which +<p>The url to your project's issue tracker and / or the email address to which issues should be reported. These are helpful for people who encounter issues with your package.</p> <p>It should look like this:</p> -<pre><code>{ "url" : "http://github.com/owner/project/issues" -, "email" : "project@hostname.com" +<pre><code>{ "url" : "http://github.com/owner/project/issues" +, "email" : "project@hostname.com" }</code></pre> <p>You can specify either one or both values. If you want to provide only a url, -you can specify the value for "bugs" as a simple string instead of an object.</p> +you can specify the value for "bugs" as a simple string instead of an object.</p> <p>If a url is provided, it will be used by the <code>npm bugs</code> command.</p> <h2 id="people-fields-author-contributors">people fields: author, contributors</h2> -<p>The "author" is one person. "contributors" is an array of people. A "person" -is an object with a "name" field and optionally "url" and "email", like this:</p> +<p>The "author" is one person. "contributors" is an array of people. A "person" +is an object with a "name" field and optionally "url" and "email", like this:</p> -<pre><code>{ "name" : "Barney Rubble" -, "email" : "b@rubble.com" -, "url" : "http://barnyrubble.tumblr.com/" +<pre><code>{ "name" : "Barney Rubble" +, "email" : "b@rubble.com" +, "url" : "http://barnyrubble.tumblr.com/" }</code></pre> <p>Or you can shorten that all into a single string, and npm will parse it for you:</p> -<pre><code>"Barney Rubble <b@rubble.com> (http://barnyrubble.tumblr.com/)</code></pre> +<pre><code>"Barney Rubble <b@rubble.com> (http://barnyrubble.tumblr.com/)</code></pre> <p>Both email and url are optional either way.</p> -<p>npm also sets a top-level "maintainers" field with your npm user info.</p> +<p>npm also sets a top-level "maintainers" field with your npm user info.</p> <h2 id="files">files</h2> -<p>The "files" field is an array of files to include in your project. If +<p>The "files" field is an array of files to include in your project. If you name a folder in the array, then it will also include the files inside that folder. (Unless they would be ignored by another rule.)</p> -<p>You can also provide a ".npmignore" file in the root of your package, +<p>You can also provide a ".npmignore" file in the root of your package, which will keep files from being included, even if they would be picked -up by the files array. The ".npmignore" file works just like a -".gitignore".</p> +up by the files array. The ".npmignore" file works just like a +".gitignore".</p> <h2 id="main">main</h2> <p>The main field is a module ID that is the primary entry point to your program. That is, if your package is named <code>foo</code>, and a user installs it, and then does -<code>require("foo")</code>, then your main module's exports object will be returned.</p> +<code>require("foo")</code>, then your main module's exports object will be returned.</p> <p>This should be a module ID relative to the root of your package folder.</p> @@ -148,9 +149,9 @@ much else.</p> <h2 id="bin">bin</h2> -<p>A lot of packages have one or more executable files that they'd like to +<p>A lot of packages have one or more executable files that they'd like to install into the PATH. npm makes this pretty easy (in fact, it uses this -feature to install the "npm" executable.)</p> +feature to install the "npm" executable.)</p> <p>To use this, supply a <code>bin</code> field in your package.json which is a map of command name to local file name. On install, npm will symlink that file into @@ -159,49 +160,49 @@ installs.</p> <p>For example, npm has this:</p> -<pre><code>{ "bin" : { "npm" : "./cli.js" } }</code></pre> +<pre><code>{ "bin" : { "npm" : "./cli.js" } }</code></pre> -<p>So, when you install npm, it'll create a symlink from the <code>cli.js</code> script to +<p>So, when you install npm, it'll create a symlink from the <code>cli.js</code> script to <code>/usr/local/bin/npm</code>.</p> <p>If you have a single executable, and its name should be the name of the package, then you can just supply it as a string. For example:</p> -<pre><code>{ "name": "my-program" -, "version": "1.2.5" -, "bin": "./path/to/program" }</code></pre> +<pre><code>{ "name": "my-program" +, "version": "1.2.5" +, "bin": "./path/to/program" }</code></pre> <p>would be the same as this:</p> -<pre><code>{ "name": "my-program" -, "version": "1.2.5" -, "bin" : { "my-program" : "./path/to/program" } }</code></pre> +<pre><code>{ "name": "my-program" +, "version": "1.2.5" +, "bin" : { "my-program" : "./path/to/program" } }</code></pre> <h2 id="man">man</h2> <p>Specify either a single file or an array of filenames to put in place for the <code>man</code> program to find.</p> -<p>If only a single file is provided, then it's installed such that it is the +<p>If only a single file is provided, then it's installed such that it is the result from <code>man <pkgname></code>, regardless of its actual filename. For example:</p> -<pre><code>{ "name" : "foo" -, "version" : "1.2.3" -, "description" : "A packaged foo fooer for fooing foos" -, "main" : "foo.js" -, "man" : "./man/doc.1" +<pre><code>{ "name" : "foo" +, "version" : "1.2.3" +, "description" : "A packaged foo fooer for fooing foos" +, "main" : "foo.js" +, "man" : "./man/doc.1" }</code></pre> <p>would link the <code>./man/doc.1</code> file in such that it is the target for <code>man foo</code></p> -<p>If the filename doesn't start with the package name, then it's prefixed. +<p>If the filename doesn't start with the package name, then it's prefixed. So, this:</p> -<pre><code>{ "name" : "foo" -, "version" : "1.2.3" -, "description" : "A packaged foo fooer for fooing foos" -, "main" : "foo.js" -, "man" : [ "./man/foo.1", "./man/bar.1" ] +<pre><code>{ "name" : "foo" +, "version" : "1.2.3" +, "description" : "A packaged foo fooer for fooing foos" +, "main" : "foo.js" +, "man" : [ "./man/foo.1", "./man/bar.1" ] }</code></pre> <p>will create files to do <code>man foo</code> and <code>man foo-bar</code>.</p> @@ -209,11 +210,11 @@ So, this:</p> <p>Man files must end with a number, and optionally a <code>.gz</code> suffix if they are compressed. The number dictates which man section the file is installed into.</p> -<pre><code>{ "name" : "foo" -, "version" : "1.2.3" -, "description" : "A packaged foo fooer for fooing foos" -, "main" : "foo.js" -, "man" : [ "./man/foo.1", "./man/foo.2" ] +<pre><code>{ "name" : "foo" +, "version" : "1.2.3" +, "description" : "A packaged foo fooer for fooing foos" +, "main" : "foo.js" +, "man" : [ "./man/foo.1", "./man/foo.2" ] }</code></pre> <p>will create entries for <code>man foo</code> and <code>man 2 foo</code></p> @@ -222,26 +223,26 @@ compressed. The number dictates which man section the file is installed into.</ <p>The CommonJS <a href="http://wiki.commonjs.org/wiki/Packages/1.0">Packages</a> spec details a few ways that you can indicate the structure of your package using a <code>directories</code> -hash. If you look at <a href="http://registry.npmjs.org/npm/latest">npm's package.json</a>, -you'll see that it has directories for doc, lib, and man.</p> +hash. If you look at <a href="http://registry.npmjs.org/npm/latest">npm's package.json</a>, +you'll see that it has directories for doc, lib, and man.</p> <p>In the future, this information may be used in other creative ways.</p> <h3 id="directories-lib">directories.lib</h3> <p>Tell people where the bulk of your library is. Nothing special is done -with the lib folder in any way, but it's useful meta info.</p> +with the lib folder in any way, but it's useful meta info.</p> <h3 id="directories-bin">directories.bin</h3> -<p>If you specify a "bin" directory, then all the files in that folder will -be used as the "bin" hash.</p> +<p>If you specify a "bin" directory, then all the files in that folder will +be used as the "bin" hash.</p> -<p>If you have a "bin" hash already, then this has no effect.</p> +<p>If you have a "bin" hash already, then this has no effect.</p> <h3 id="directories-man">directories.man</h3> -<p>A folder that is full of man pages. Sugar to generate a "man" array by +<p>A folder that is full of man pages. Sugar to generate a "man" array by walking the folder.</p> <h3 id="directories-doc">directories.doc</h3> @@ -261,23 +262,23 @@ command will be able to find you.</p> <p>Do it like this:</p> -<pre><code>"repository" : - { "type" : "git" - , "url" : "http://github.com/isaacs/npm.git" +<pre><code>"repository" : + { "type" : "git" + , "url" : "http://github.com/isaacs/npm.git" } -"repository" : - { "type" : "svn" - , "url" : "http://v8.googlecode.com/svn/trunk/" +"repository" : + { "type" : "svn" + , "url" : "http://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> +html project page that you put in your browser. It's for computers.</p> <h2 id="scripts">scripts</h2> -<p>The "scripts" member is an object hash of script commands that are run +<p>The "scripts" member is an object hash of script commands that are run at various times in the lifecycle of your package. The key is the lifecycle event, and the value is the command to run at that point.</p> @@ -285,14 +286,14 @@ event, and the value is the command to run at that point.</p> <h2 id="config">config</h2> -<p>A "config" hash can be used to set configuration +<p>A "config" hash can be used to set configuration parameters used in package scripts that persist across upgrades. For instance, if a package had the following:</p> -<pre><code>{ "name" : "foo" -, "config" : { "port" : "8080" } }</code></pre> +<pre><code>{ "name" : "foo" +, "config" : { "port" : "8080" } }</code></pre> -<p>and then had a "start" command that then referenced the +<p>and then had a "start" command that then referenced the <code>npm_package_config_port</code> environment variable, then the user could override that by doing <code>npm config set foo:port 8001</code>.</p> @@ -303,29 +304,29 @@ configs.</p> <p>Dependencies are specified with a simple hash of package name to version range. The version range is EITHER a string which has one or more -space-separated descriptors, OR a range like "fromVersion - toVersion"</p> +space-separated descriptors, OR a range like "fromVersion - toVersion"</p> <p><strong>Please do not put test harnesses in your <code>dependencies</code> hash.</strong> See <code>devDependencies</code>, below.</p> -<p>Version range descriptors may be any of the following styles, where "version" +<p>Version range descriptors may be any of the following styles, where "version" is a semver compatible version identifier.</p> -<ul><li><code>version</code> Must match <code>version</code> exactly</li><li><code>=version</code> Same as just <code>version</code></li><li><code>>version</code> Must be greater than <code>version</code></li><li><code>>=version</code> etc</li><li><code><version</code></li><li><code><=version</code></li><li><code>~version</code> See 'Tilde Version Ranges' below</li><li><code>1.2.x</code> See 'X Version Ranges' below</li><li><code>http://...</code> See 'URLs as Dependencies' below</li><li><code>*</code> Matches any version</li><li><code>""</code> (just an empty string) Same as <code>*</code></li><li><code>version1 - version2</code> Same as <code>>=version1 <=version2</code>.</li><li><code>range1 || range2</code> Passes if either range1 or range2 are satisfied.</li><li><code>git...</code> See 'Git URLs as Dependencies' below</li></ul> +<ul><li><code>version</code> Must match <code>version</code> exactly</li><li><code>=version</code> Same as just <code>version</code></li><li><code>>version</code> Must be greater than <code>version</code></li><li><code>>=version</code> etc</li><li><code><version</code></li><li><code><=version</code></li><li><code>~version</code> See 'Tilde Version Ranges' below</li><li><code>1.2.x</code> See 'X Version Ranges' below</li><li><code>http://...</code> See 'URLs as Dependencies' below</li><li><code>*</code> Matches any version</li><li><code>""</code> (just an empty string) Same as <code>*</code></li><li><code>version1 - version2</code> Same as <code>>=version1 <=version2</code>.</li><li><code>range1 || range2</code> Passes if either range1 or range2 are satisfied.</li><li><code>git...</code> See 'Git URLs as Dependencies' below</li></ul> <p>For example, these are all valid:</p> -<pre><code>{ "dependencies" : - { "foo" : "1.0.0 - 2.9999.9999" - , "bar" : ">=1.0.2 <2.1.2" - , "baz" : ">1.0.2 <=2.3.4" - , "boo" : "2.0.1" - , "qux" : "<1.0.0 || >=2.3.1 <2.4.5 || >=2.5.2 <3.0.0" - , "asd" : "http://asdf.com/asdf.tar.gz" - , "til" : "~1.2" - , "elf" : "~1.2.3" - , "two" : "2.x" - , "thr" : "3.3.x" +<pre><code>{ "dependencies" : + { "foo" : "1.0.0 - 2.9999.9999" + , "bar" : ">=1.0.2 <2.1.2" + , "baz" : ">1.0.2 <=2.3.4" + , "boo" : "2.0.1" + , "qux" : "<1.0.0 || >=2.3.1 <2.4.5 || >=2.5.2 <3.0.0" + , "asd" : "http://asdf.com/asdf.tar.gz" + , "til" : "~1.2" + , "elf" : "~1.2.3" + , "two" : "2.x" + , "thr" : "3.3.x" } }</code></pre> @@ -338,19 +339,19 @@ a version in the following fashion.</p> <p>For example, the following are equivalent:</p> -<ul><li><code>"~1.2.3" = ">=1.2.3 <1.3.0"</code></li><li><code>"~1.2" = ">=1.2.0 <2.0.0"</code></li><li><code>"~1" = ">=1.0.0 <2.0.0"</code></li></ul> +<ul><li><code>"~1.2.3" = ">=1.2.3 <1.3.0"</code></li><li><code>"~1.2" = ">=1.2.0 <2.0.0"</code></li><li><code>"~1" = ">=1.0.0 <2.0.0"</code></li></ul> <h3 id="X-Version-Ranges">X Version Ranges</h3> -<p>An "x" in a version range specifies that the version number must start +<p>An "x" in a version range specifies that the version number must start with the supplied digits, but any digit may be used in place of the x.</p> <p>The following are equivalent:</p> -<ul><li><code>"1.2.x" = ">=1.2.0 <1.3.0"</code></li><li><code>"1.x.x" = ">=1.0.0 <2.0.0"</code></li><li><code>"1.2" = "1.2.x"</code></li><li><code>"1.x" = "1.x.x"</code></li><li><code>"1" = "1.x.x"</code></li></ul> +<ul><li><code>"1.2.x" = ">=1.2.0 <1.3.0"</code></li><li><code>"1.x.x" = ">=1.0.0 <2.0.0"</code></li><li><code>"1.2" = "1.2.x"</code></li><li><code>"1.x" = "1.x.x"</code></li><li><code>"1" = "1.x.x"</code></li></ul> <p>You may not supply a comparator with a version containing an x. Any -digits after the first "x" are ignored.</p> +digits after the first "x" are ignored.</p> <h3 id="URLs-as-Dependencies">URLs as Dependencies</h3> @@ -376,10 +377,10 @@ an argument to <code>git checkout</code>. The default is <code>master</code>.</ <h2 id="devDependencies">devDependencies</h2> <p>If someone is planning on downloading and using your module in their -program, then they probably don't want or need to download and build +program, then they probably don't want or need to download and build the external test or documentation framework that you use.</p> -<p>In this case, it's best to list these additional items in a +<p>In this case, it's best to list these additional items in a <code>devDependencies</code> hash.</p> <p>These things will be installed whenever the <code>--dev</code> configuration flag @@ -391,7 +392,7 @@ for more on the topic.</p> <p>Array of package names that will be bundled when publishing the package.</p> -<p>If this is spelled <code>"bundleDependencies"</code>, then that is also honorable.</p> +<p>If this is spelled <code>"bundleDependencies"</code>, then that is also honorable.</p> <h2 id="optionalDependencies">optionalDependencies</h2> @@ -401,12 +402,12 @@ cannot be found or fails to install, then you may put it in the or url, just like the <code>dependencies</code> hash. The difference is that failure is tolerated.</p> -<p>It is still your program's responsibility to handle the lack of the +<p>It is still your program's responsibility to handle the lack of the dependency. For example, something like this:</p> <pre><code>try { - var foo = require('foo') - var fooVersion = require('foo/package.json').version + var foo = require('foo') + var fooVersion = require('foo/package.json').version } catch (er) { foo = null } @@ -421,25 +422,25 @@ if (foo) { }</code></pre> <p>Entries in <code>optionalDependencies</code> will override entries of the same name in -<code>dependencies</code>, so it's usually best to only put in one place.</p> +<code>dependencies</code>, so it's usually best to only put in one place.</p> <h2 id="engines">engines</h2> <p>You can specify the version of node that your stuff works on:</p> -<pre><code>{ "engines" : { "node" : ">=0.1.27 <0.1.30" } }</code></pre> +<pre><code>{ "engines" : { "node" : ">=0.1.27 <0.1.30" } }</code></pre> -<p>And, like with dependencies, if you don't specify the version (or if you -specify "*" as the version), then any version of node will do.</p> +<p>And, like with dependencies, if you don't specify the version (or if you +specify "*" as the version), then any version of node will do.</p> -<p>If you specify an "engines" field, then npm will require that "node" be -somewhere on that list. If "engines" is omitted, then npm will just assume +<p>If you specify an "engines" field, then npm will require that "node" be +somewhere on that list. If "engines" is omitted, then npm will just assume that it works on node.</p> -<p>You can also use the "engines" field to specify which versions of npm +<p>You can also use the "engines" field to specify which versions of npm are capable of properly installing your program. For example:</p> -<pre><code>{ "engines" : { "npm" : "~1.0.20" } }</code></pre> +<pre><code>{ "engines" : { "npm" : "~1.0.20" } }</code></pre> <p>Note that, unless the user has set the <code>engine-strict</code> config flag, this field is advisory only.</p> @@ -448,8 +449,8 @@ field is advisory only.</p> <p>If you are sure that your module will <em>definitely not</em> run properly on versions of Node/npm other than those specified in the <code>engines</code> hash, -then you can set <code>"engineStrict": true</code> in your package.json file. -This will override the user's <code>engine-strict</code> config setting.</p> +then you can set <code>"engineStrict": true</code> in your package.json file. +This will override the user's <code>engine-strict</code> config setting.</p> <p>Please do not do this unless you are really very very sure. If your engines hash is something overly restrictive, you can quite easily and @@ -462,16 +463,16 @@ people abuse it, it will be removed in a future version of npm.</p> <p>You can specify which operating systems your module will run on:</p> -<pre><code>"os" : [ "darwin", "linux" ]</code></pre> +<pre><code>"os" : [ "darwin", "linux" ]</code></pre> <p>You can also blacklist instead of whitelist operating systems, -just prepend the blacklisted os with a '!':</p> +just prepend the blacklisted os with a '!':</p> -<pre><code>"os" : [ "!win32" ]</code></pre> +<pre><code>"os" : [ "!win32" ]</code></pre> <p>The host operating system is determined by <code>process.platform</code></p> -<p>It is allowed to both blacklist, and whitelist, although there isn't any +<p>It is allowed to both blacklist, and whitelist, although there isn't any good reason to do this.</p> <h2 id="cpu">cpu</h2> @@ -479,11 +480,11 @@ good reason to do this.</p> <p>If your code only runs on certain cpu architectures, you can specify which ones.</p> -<pre><code>"cpu" : [ "x64", "ia32" ]</code></pre> +<pre><code>"cpu" : [ "x64", "ia32" ]</code></pre> <p>Like the <code>os</code> option, you can also blacklist architectures:</p> -<pre><code>"cpu" : [ "!arm", "!mips" ]</code></pre> +<pre><code>"cpu" : [ "!arm", "!mips" ]</code></pre> <p>The host architecture is determined by <code>process.arch</code></p> @@ -493,12 +494,12 @@ you can specify which ones.</p> installed globally, then set this value to <code>true</code> to provide a warning if it is installed locally.</p> -<p>It doesn't actually prevent users from installing it locally, but it -does help prevent some confusion if it doesn't work as expected.</p> +<p>It doesn't actually prevent users from installing it locally, but it +does help prevent some confusion if it doesn't work as expected.</p> <h2 id="private">private</h2> -<p>If you set <code>"private": true</code> in your package.json, then npm will refuse +<p>If you set <code>"private": true</code> in your package.json, then npm will refuse to publish it.</p> <p>This is a way to prevent accidental publication of private repositories. @@ -509,13 +510,13 @@ to override the <code>registry</code> config param at publish-time.</p> <h2 id="publishConfig">publishConfig</h2> -<p>This is a set of config values that will be used at publish-time. It's +<p>This is a set of config values that will be used at publish-time. It's especially handy if you want to set the tag or registry, so that you can -ensure that a given package is not tagged with "latest" or published to +ensure that a given package is not tagged with "latest" or published to the global public registry by default.</p> -<p>Any config values can be overridden, but of course only "tag" and -"registry" probably matter for the purposes of publishing.</p> +<p>Any config values can be overridden, but of course only "tag" and +"registry" probably matter for the purposes of publishing.</p> <p>See <code><a href="../doc/config.html">config(1)</a></code> to see the list of config options that can be overridden.</p> @@ -524,7 +525,7 @@ overridden.</p> <ul><li><a href="../doc/semver.html">semver(1)</a></li><li><a href="../doc/init.html">init(1)</a></li><li><a href="../doc/version.html">version(1)</a></li><li><a href="../doc/config.html">config(1)</a></li><li><a href="../doc/help.html">help(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/publish.html">publish(1)</a></li><li><a href="../doc/rm.html">rm(1)</a></li></ul> </div> -<p id="footer">json — npm@1.1.46</p> +<p id="footer">json — npm@1.1.49</p> <script> ;(function () { var wrapper = document.getElementById("wrapper") |