@ -107,6 +107,27 @@ you can specify the value for "bugs" as a simple string instead of an
< p > If a url is provided, it will be used by the < code > npm bugs< / code > command.< / p > < p > If a url is provided, it will be used by the < code > npm bugs< / code > command.< / p >
< h2 id = "license" > license< / h2 >
< p > You should specify a license for your package so that people know how they are
permitted to use it, and any restrictions you' re placing on it.< / p >
< p > The simplest way, assuming you' re using a common license such as BSD or MIT, is
to just specify the name of the license you' re using, like this:< / p >
< pre > < code > { " license" : " BSD" }< / code > < / pre >
< p > If you have more complex licensing terms, or you want to provide more detail
in your package.json file, you can use the more verbose plural form, like this:< / p >
< pre > < code > " licenses" : [
{ " type" : " MyLicense"
, " url" : " http://github.com/owner/project/path/to/license"
}
]< / code > < / pre >
< p > It' s also a good idea to include a license file at the top level in your package.< / p >
< h2 id = "people-fields-author-contributors" > people fields: author, contributors< / h2 > < 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" < p > The " author" is one person. " contributors" is an array of people. A " person"
@ -384,9 +405,9 @@ the external test or documentation framework that you use.</p>
< code > devDependencies< / code > hash.< / p > < code > devDependencies< / code > hash.< / p >
< p > These things will be installed whenever the < code > --dev< / code > configuration flag< p > These things will be installed whenever the < code > --dev< / code > configuration flag
is set. This flag is set automatically when doing < code > npm link< / code > , and can is set. This flag is set automatically when doing < code > npm link< / code > or when doing
be managed like any other npm configuration param. See < code > < a href = "../doc/config.html" > config(1)< / a > < / code > < code > npm install< / code > from the root of a package, and can be managed like any other npm
for more on the topic.< / p > configuration param. See < code > < a href = "../doc/config.html" > config(1)< / a > < / code > for more on the topic.< / p >
< h2 id = "bundledDependencies" > bundledDependencies< / h2 > < h2 id = "bundledDependencies" > bundledDependencies< / h2 >
@ -525,7 +546,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 > < 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 > < / div >
< p id = "footer" > json — npm@1.2.14 < / p > < p id = "footer" > json — npm@1.2.15 < / p >
< script > < script >
;(function () {;(function () {
var wrapper = document.getElementById("wrapper")var wrapper = document.getElementById("wrapper")
isaacs
12 years ago