Simple email application for Android. Original source code: https://framagit.org/dystopia-project/simple-email
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

797 lines
25 KiB

  1. package.json(5) -- Specifics of npm's package.json handling
  2. ===========================================================
  3. ## DESCRIPTION
  4. This document is all you need to know about what's required in your package.json
  5. file. It must be actual JSON, not just a JavaScript object literal.
  6. A lot of the behavior described in this document is affected by the config
  7. settings described in `npm-config(7)`.
  8. ## name
  9. If you plan to publish your package, the *most* important things in your
  10. package.json are the name and version fields as they will be required. The name
  11. and version together form an identifier that is assumed to be completely unique.
  12. Changes to the package should come along with changes to the version. If you don't
  13. plan to publish your package, the name and version fields are optional.
  14. The name is what your thing is called.
  15. Some rules:
  16. * The name must be less than or equal to 214 characters. This includes the scope for
  17. scoped packages.
  18. * The name can't start with a dot or an underscore.
  19. * New packages must not have uppercase letters in the name.
  20. * The name ends up being part of a URL, an argument on the command line, and a
  21. folder name. Therefore, the name can't contain any non-URL-safe characters.
  22. Some tips:
  23. * Don't use the same name as a core Node module.
  24. * Don't put "js" or "node" in the name. It's assumed that it's js, since you're
  25. writing a package.json file, and you can specify the engine using the "engines"
  26. field. (See below.)
  27. * The name will probably be passed as an argument to require(), so it should
  28. be something short, but also reasonably descriptive.
  29. * You may want to check the npm registry to see if there's something by that name
  30. already, before you get too attached to it. <https://www.npmjs.com/>
  31. A name can be optionally prefixed by a scope, e.g. `@myorg/mypackage`. See
  32. `npm-scope(7)` for more detail.
  33. ## version
  34. If you plan to publish your package, the *most* important things in your
  35. package.json are the name and version fields as they will be required. The name
  36. and version together form an identifier that is assumed to be completely unique.
  37. Changes to the package should come along with changes to the version. If you don't
  38. plan to publish your package, the name and version fields are optional.
  39. Version must be parseable by
  40. [node-semver](https://github.com/isaacs/node-semver), which is bundled
  41. with npm as a dependency. (`npm install semver` to use it yourself.)
  42. More on version numbers and ranges at semver(7).
  43. ## description
  44. Put a description in it. It's a string. This helps people discover your
  45. package, as it's listed in `npm search`.
  46. ## keywords
  47. Put keywords in it. It's an array of strings. This helps people
  48. discover your package as it's listed in `npm search`.
  49. ## homepage
  50. The url to the project homepage.
  51. Example:
  52. "homepage": "https://github.com/owner/project#readme"
  53. ## bugs
  54. The url to your project's issue tracker and / or the email address to which
  55. issues should be reported. These are helpful for people who encounter issues
  56. with your package.
  57. It should look like this:
  58. { "url" : "https://github.com/owner/project/issues"
  59. , "email" : "project@hostname.com"
  60. }
  61. You can specify either one or both values. If you want to provide only a url,
  62. you can specify the value for "bugs" as a simple string instead of an object.
  63. If a url is provided, it will be used by the `npm bugs` command.
  64. ## license
  65. You should specify a license for your package so that people know how they are
  66. permitted to use it, and any restrictions you're placing on it.
  67. If you're using a common license such as BSD-2-Clause or MIT, add a
  68. current SPDX license identifier for the license you're using, like this:
  69. { "license" : "BSD-3-Clause" }
  70. You can check [the full list of SPDX license IDs](https://spdx.org/licenses/).
  71. Ideally you should pick one that is
  72. [OSI](https://opensource.org/licenses/alphabetical) approved.
  73. If your package is licensed under multiple common licenses, use an [SPDX license
  74. expression syntax version 2.0 string](https://www.npmjs.com/package/spdx), like this:
  75. { "license" : "(ISC OR GPL-3.0)" }
  76. If you are using a license that hasn't been assigned an SPDX identifier, or if
  77. you are using a custom license, use a string value like this one:
  78. { "license" : "SEE LICENSE IN <filename>" }
  79. Then include a file named `<filename>` at the top level of the package.
  80. Some old packages used license objects or a "licenses" property containing an
  81. array of license objects:
  82. // Not valid metadata
  83. { "license" :
  84. { "type" : "ISC"
  85. , "url" : "https://opensource.org/licenses/ISC"
  86. }
  87. }
  88. // Not valid metadata
  89. { "licenses" :
  90. [
  91. { "type": "MIT"
  92. , "url": "https://www.opensource.org/licenses/mit-license.php"
  93. }
  94. , { "type": "Apache-2.0"
  95. , "url": "https://opensource.org/licenses/apache2.0.php"
  96. }
  97. ]
  98. }
  99. Those styles are now deprecated. Instead, use SPDX expressions, like this:
  100. { "license": "ISC" }
  101. { "license": "(MIT OR Apache-2.0)" }
  102. Finally, if you do not wish to grant others the right to use a private or
  103. unpublished package under any terms:
  104. { "license": "UNLICENSED" }
  105. Consider also setting `"private": true` to prevent accidental publication.
  106. ## people fields: author, contributors
  107. The "author" is one person. "contributors" is an array of people. A "person"
  108. is an object with a "name" field and optionally "url" and "email", like this:
  109. { "name" : "Barney Rubble"
  110. , "email" : "b@rubble.com"
  111. , "url" : "http://barnyrubble.tumblr.com/"
  112. }
  113. Or you can shorten that all into a single string, and npm will parse it for you:
  114. "Barney Rubble <b@rubble.com> (http://barnyrubble.tumblr.com/)"
  115. Both email and url are optional either way.
  116. npm also sets a top-level "maintainers" field with your npm user info.
  117. ## files
  118. The optional `files` field is an array of file patterns that describes
  119. the entries to be included when your package is installed as a
  120. dependency. File patterns follow a similar syntax to `.gitignore`, but
  121. reversed: including a file, directory, or glob pattern (`*`, `**/*`, and such)
  122. will make it so that file is included in the tarball when it's packed. Omitting
  123. the field will make it default to `["*"]`, which means it will include all files.
  124. Some special files and directories are also included or excluded regardless of
  125. whether they exist in the `files` array (see below).
  126. You can also provide a `.npmignore` file in the root of your package or
  127. in subdirectories, which will keep files from being included. At the
  128. root of your package it will not override the "files" field, but in
  129. subdirectories it will. The `.npmignore` file works just like a
  130. `.gitignore`. If there is a `.gitignore` file, and `.npmignore` is
  131. missing, `.gitignore`'s contents will be used instead.
  132. Files included with the "package.json#files" field _cannot_ be excluded
  133. through `.npmignore` or `.gitignore`.
  134. Certain files are always included, regardless of settings:
  135. * `package.json`
  136. * `README`
  137. * `CHANGES` / `CHANGELOG` / `HISTORY`
  138. * `LICENSE` / `LICENCE`
  139. * `NOTICE`
  140. * The file in the "main" field
  141. `README`, `CHANGES`, `LICENSE` & `NOTICE` can have any case and extension.
  142. Conversely, some files are always ignored:
  143. * `.git`
  144. * `CVS`
  145. * `.svn`
  146. * `.hg`
  147. * `.lock-wscript`
  148. * `.wafpickle-N`
  149. * `.*.swp`
  150. * `.DS_Store`
  151. * `._*`
  152. * `npm-debug.log`
  153. * `.npmrc`
  154. * `node_modules`
  155. * `config.gypi`
  156. * `*.orig`
  157. * `package-lock.json` (use shrinkwrap instead)
  158. ## main
  159. The main field is a module ID that is the primary entry point to your program.
  160. That is, if your package is named `foo`, and a user installs it, and then does
  161. `require("foo")`, then your main module's exports object will be returned.
  162. This should be a module ID relative to the root of your package folder.
  163. For most modules, it makes the most sense to have a main script and often not
  164. much else.
  165. ## browser
  166. If your module is meant to be used client-side the browser field should be
  167. used instead of the main field. This is helpful to hint users that it might
  168. rely on primitives that aren't available in Node.js modules. (e.g. `window`)
  169. ## bin
  170. A lot of packages have one or more executable files that they'd like to
  171. install into the PATH. npm makes this pretty easy (in fact, it uses this
  172. feature to install the "npm" executable.)
  173. To use this, supply a `bin` field in your package.json which is a map of
  174. command name to local file name. On install, npm will symlink that file into
  175. `prefix/bin` for global installs, or `./node_modules/.bin/` for local
  176. installs.
  177. For example, myapp could have this:
  178. { "bin" : { "myapp" : "./cli.js" } }
  179. So, when you install myapp, it'll create a symlink from the `cli.js` script to
  180. `/usr/local/bin/myapp`.
  181. If you have a single executable, and its name should be the name
  182. of the package, then you can just supply it as a string. For example:
  183. { "name": "my-program"
  184. , "version": "1.2.5"
  185. , "bin": "./path/to/program" }
  186. would be the same as this:
  187. { "name": "my-program"
  188. , "version": "1.2.5"
  189. , "bin" : { "my-program" : "./path/to/program" } }
  190. Please make sure that your file(s) referenced in `bin` starts with
  191. `#!/usr/bin/env node`, otherwise the scripts are started without the node
  192. executable!
  193. ## man
  194. Specify either a single file or an array of filenames to put in place for the
  195. `man` program to find.
  196. If only a single file is provided, then it's installed such that it is the
  197. result from `man <pkgname>`, regardless of its actual filename. For example:
  198. { "name" : "foo"
  199. , "version" : "1.2.3"
  200. , "description" : "A packaged foo fooer for fooing foos"
  201. , "main" : "foo.js"
  202. , "man" : "./man/doc.1"
  203. }
  204. would link the `./man/doc.1` file in such that it is the target for `man foo`
  205. If the filename doesn't start with the package name, then it's prefixed.
  206. So, this:
  207. { "name" : "foo"
  208. , "version" : "1.2.3"
  209. , "description" : "A packaged foo fooer for fooing foos"
  210. , "main" : "foo.js"
  211. , "man" : [ "./man/foo.1", "./man/bar.1" ]
  212. }
  213. will create files to do `man foo` and `man foo-bar`.
  214. Man files must end with a number, and optionally a `.gz` suffix if they are
  215. compressed. The number dictates which man section the file is installed into.
  216. { "name" : "foo"
  217. , "version" : "1.2.3"
  218. , "description" : "A packaged foo fooer for fooing foos"
  219. , "main" : "foo.js"
  220. , "man" : [ "./man/foo.1", "./man/foo.2" ]
  221. }
  222. will create entries for `man foo` and `man 2 foo`
  223. ## directories
  224. The CommonJS [Packages](http://wiki.commonjs.org/wiki/Packages/1.0) spec details a
  225. few ways that you can indicate the structure of your package using a `directories`
  226. object. If you look at [npm's package.json](https://registry.npmjs.org/npm/latest),
  227. you'll see that it has directories for doc, lib, and man.
  228. In the future, this information may be used in other creative ways.
  229. ### directories.lib
  230. Tell people where the bulk of your library is. Nothing special is done
  231. with the lib folder in any way, but it's useful meta info.
  232. ### directories.bin
  233. If you specify a `bin` directory in `directories.bin`, all the files in
  234. that folder will be added.
  235. Because of the way the `bin` directive works, specifying both a
  236. `bin` path and setting `directories.bin` is an error. If you want to
  237. specify individual files, use `bin`, and for all the files in an
  238. existing `bin` directory, use `directories.bin`.
  239. ### directories.man
  240. A folder that is full of man pages. Sugar to generate a "man" array by
  241. walking the folder.
  242. ### directories.doc
  243. Put markdown files in here. Eventually, these will be displayed nicely,
  244. maybe, someday.
  245. ### directories.example
  246. Put example scripts in here. Someday, it might be exposed in some clever way.
  247. ### directories.test
  248. Put your tests in here. It is currently not exposed, but it might be in the
  249. future.
  250. ## repository
  251. Specify the place where your code lives. This is helpful for people who
  252. want to contribute. If the git repo is on GitHub, then the `npm docs`
  253. command will be able to find you.
  254. Do it like this:
  255. "repository": {
  256. "type" : "git",
  257. "url" : "https://github.com/npm/cli.git"
  258. }
  259. "repository": {
  260. "type" : "svn",
  261. "url" : "https://v8.googlecode.com/svn/trunk/"
  262. }
  263. The URL should be a publicly available (perhaps read-only) url that can be handed
  264. directly to a VCS program without any modification. It should not be a url to an
  265. html project page that you put in your browser. It's for computers.
  266. For GitHub, GitHub gist, Bitbucket, or GitLab repositories you can use the same
  267. shortcut syntax you use for `npm install`:
  268. "repository": "npm/npm"
  269. "repository": "github:user/repo"
  270. "repository": "gist:11081aaa281"
  271. "repository": "bitbucket:user/repo"
  272. "repository": "gitlab:user/repo"
  273. ## scripts
  274. The "scripts" property is a dictionary containing script commands that are run
  275. at various times in the lifecycle of your package. The key is the lifecycle
  276. event, and the value is the command to run at that point.
  277. See `npm-scripts(7)` to find out more about writing package scripts.
  278. ## config
  279. A "config" object can be used to set configuration parameters used in package
  280. scripts that persist across upgrades. For instance, if a package had the
  281. following:
  282. { "name" : "foo"
  283. , "config" : { "port" : "8080" } }
  284. and then had a "start" command that then referenced the
  285. `npm_package_config_port` environment variable, then the user could
  286. override that by doing `npm config set foo:port 8001`.
  287. See `npm-config(7)` and `npm-scripts(7)` for more on package
  288. configs.
  289. ## dependencies
  290. Dependencies are specified in a simple object that maps a package name to a
  291. version range. The version range is a string which has one or more
  292. space-separated descriptors. Dependencies can also be identified with a
  293. tarball or git URL.
  294. **Please do not put test harnesses or transpilers in your
  295. `dependencies` object.** See `devDependencies`, below.
  296. See semver(7) for more details about specifying version ranges.
  297. * `version` Must match `version` exactly
  298. * `>version` Must be greater than `version`
  299. * `>=version` etc
  300. * `<version`
  301. * `<=version`
  302. * `~version` "Approximately equivalent to version" See semver(7)
  303. * `^version` "Compatible with version" See semver(7)
  304. * `1.2.x` 1.2.0, 1.2.1, etc., but not 1.3.0
  305. * `http://...` See 'URLs as Dependencies' below
  306. * `*` Matches any version
  307. * `""` (just an empty string) Same as `*`
  308. * `version1 - version2` Same as `>=version1 <=version2`.
  309. * `range1 || range2` Passes if either range1 or range2 are satisfied.
  310. * `git...` See 'Git URLs as Dependencies' below
  311. * `user/repo` See 'GitHub URLs' below
  312. * `tag` A specific version tagged and published as `tag` See `npm-dist-tag(1)`
  313. * `path/path/path` See [Local Paths](#local-paths) below
  314. For example, these are all valid:
  315. { "dependencies" :
  316. { "foo" : "1.0.0 - 2.9999.9999"
  317. , "bar" : ">=1.0.2 <2.1.2"
  318. , "baz" : ">1.0.2 <=2.3.4"
  319. , "boo" : "2.0.1"
  320. , "qux" : "<1.0.0 || >=2.3.1 <2.4.5 || >=2.5.2 <3.0.0"
  321. , "asd" : "http://asdf.com/asdf.tar.gz"
  322. , "til" : "~1.2"
  323. , "elf" : "~1.2.3"
  324. , "two" : "2.x"
  325. , "thr" : "3.3.x"
  326. , "lat" : "latest"
  327. , "dyl" : "file:../dyl"
  328. }
  329. }
  330. ### URLs as Dependencies
  331. You may specify a tarball URL in place of a version range.
  332. This tarball will be downloaded and installed locally to your package at
  333. install time.
  334. ### Git URLs as Dependencies
  335. Git urls are of the form:
  336. <protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>[#<commit-ish> | #semver:<semver>]
  337. `<protocol>` is one of `git`, `git+ssh`, `git+http`, `git+https`, or
  338. `git+file`.
  339. If `#<commit-ish>` is provided, it will be used to clone exactly that
  340. commit. If the commit-ish has the format `#semver:<semver>`, `<semver>` can
  341. be any valid semver range or exact version, and npm will look for any tags
  342. or refs matching that range in the remote repository, much as it would for a
  343. registry dependency. If neither `#<commit-ish>` or `#semver:<semver>` is
  344. specified, then `master` is used.
  345. Examples:
  346. git+ssh://git@github.com:npm/cli.git#v1.0.27
  347. git+ssh://git@github.com:npm/cli#semver:^5.0
  348. git+https://isaacs@github.com/npm/cli.git
  349. git://github.com/npm/cli.git#v1.0.27
  350. ### GitHub URLs
  351. As of version 1.1.65, you can refer to GitHub urls as just "foo":
  352. "user/foo-project". Just as with git URLs, a `commit-ish` suffix can be
  353. included. For example:
  354. {
  355. "name": "foo",
  356. "version": "0.0.0",
  357. "dependencies": {
  358. "express": "expressjs/express",
  359. "mocha": "mochajs/mocha#4727d357ea",
  360. "module": "user/repo#feature\/branch"
  361. }
  362. }
  363. ### Local Paths
  364. As of version 2.0.0 you can provide a path to a local directory that contains a
  365. package. Local paths can be saved using `npm install -S` or
  366. `npm install --save`, using any of these forms:
  367. ../foo/bar
  368. ~/foo/bar
  369. ./foo/bar
  370. /foo/bar
  371. in which case they will be normalized to a relative path and added to your
  372. `package.json`. For example:
  373. {
  374. "name": "baz",
  375. "dependencies": {
  376. "bar": "file:../foo/bar"
  377. }
  378. }
  379. This feature is helpful for local offline development and creating
  380. tests that require npm installing where you don't want to hit an
  381. external server, but should not be used when publishing packages
  382. to the public registry.
  383. ## devDependencies
  384. If someone is planning on downloading and using your module in their
  385. program, then they probably don't want or need to download and build
  386. the external test or documentation framework that you use.
  387. In this case, it's best to map these additional items in a `devDependencies`
  388. object.
  389. These things will be installed when doing `npm link` or `npm install`
  390. from the root of a package, and can be managed like any other npm
  391. configuration param. See `npm-config(7)` for more on the topic.
  392. For build steps that are not platform-specific, such as compiling
  393. CoffeeScript or other languages to JavaScript, use the `prepare`
  394. script to do this, and make the required package a devDependency.
  395. For example:
  396. { "name": "ethopia-waza",
  397. "description": "a delightfully fruity coffee varietal",
  398. "version": "1.2.3",
  399. "devDependencies": {
  400. "coffee-script": "~1.6.3"
  401. },
  402. "scripts": {
  403. "prepare": "coffee -o lib/ -c src/waza.coffee"
  404. },
  405. "main": "lib/waza.js"
  406. }
  407. The `prepare` script will be run before publishing, so that users
  408. can consume the functionality without requiring them to compile it
  409. themselves. In dev mode (ie, locally running `npm install`), it'll
  410. run this script as well, so that you can test it easily.
  411. ## peerDependencies
  412. In some cases, you want to express the compatibility of your package with a
  413. host tool or library, while not necessarily doing a `require` of this host.
  414. This is usually referred to as a *plugin*. Notably, your module may be exposing
  415. a specific interface, expected and specified by the host documentation.
  416. For example:
  417. {
  418. "name": "tea-latte",
  419. "version": "1.3.5",
  420. "peerDependencies": {
  421. "tea": "2.x"
  422. }
  423. }
  424. This ensures your package `tea-latte` can be installed *along* with the second
  425. major version of the host package `tea` only. `npm install tea-latte` could
  426. possibly yield the following dependency graph:
  427. ├── tea-latte@1.3.5
  428. └── tea@2.2.0
  429. **NOTE: npm versions 1 and 2 will automatically install `peerDependencies` if
  430. they are not explicitly depended upon higher in the dependency tree. In the
  431. next major version of npm (npm@3), this will no longer be the case. You will
  432. receive a warning that the peerDependency is not installed instead.** The
  433. behavior in npms 1 & 2 was frequently confusing and could easily put you into
  434. dependency hell, a situation that npm is designed to avoid as much as possible.
  435. Trying to install another plugin with a conflicting requirement will cause an
  436. error. For this reason, make sure your plugin requirement is as broad as
  437. possible, and not to lock it down to specific patch versions.
  438. Assuming the host complies with [semver](https://semver.org/), only changes in
  439. the host package's major version will break your plugin. Thus, if you've worked
  440. with every 1.x version of the host package, use `"^1.0"` or `"1.x"` to express
  441. this. If you depend on features introduced in 1.5.2, use `">= 1.5.2 < 2"`.
  442. ## bundledDependencies
  443. This defines an array of package names that will be bundled when publishing
  444. the package.
  445. In cases where you need to preserve npm packages locally or have them
  446. available through a single file download, you can bundle the packages in a
  447. tarball file by specifying the package names in the `bundledDependencies`
  448. array and executing `npm pack`.
  449. For example:
  450. If we define a package.json like this:
  451. ```
  452. {
  453. "name": "awesome-web-framework",
  454. "version": "1.0.0",
  455. "bundledDependencies": [
  456. "renderized", "super-streams"
  457. ]
  458. }
  459. ```
  460. we can obtain `awesome-web-framework-1.0.0.tgz` file by running `npm pack`.
  461. This file contains the dependencies `renderized` and `super-streams` which
  462. can be installed in a new project by executing `npm install
  463. awesome-web-framework-1.0.0.tgz`.
  464. If this is spelled `"bundleDependencies"`, then that is also honored.
  465. ## optionalDependencies
  466. If a dependency can be used, but you would like npm to proceed if it cannot be
  467. found or fails to install, then you may put it in the `optionalDependencies`
  468. object. This is a map of package name to version or url, just like the
  469. `dependencies` object. The difference is that build failures do not cause
  470. installation to fail.
  471. It is still your program's responsibility to handle the lack of the
  472. dependency. For example, something like this:
  473. try {
  474. var foo = require('foo')
  475. var fooVersion = require('foo/package.json').version
  476. } catch (er) {
  477. foo = null
  478. }
  479. if ( notGoodFooVersion(fooVersion) ) {
  480. foo = null
  481. }
  482. // .. then later in your program ..
  483. if (foo) {
  484. foo.doFooThings()
  485. }
  486. Entries in `optionalDependencies` will override entries of the same name in
  487. `dependencies`, so it's usually best to only put in one place.
  488. ## engines
  489. You can specify the version of node that your stuff works on:
  490. { "engines" : { "node" : ">=0.10.3 <0.12" } }
  491. And, like with dependencies, if you don't specify the version (or if you
  492. specify "\*" as the version), then any version of node will do.
  493. If you specify an "engines" field, then npm will require that "node" be
  494. somewhere on that list. If "engines" is omitted, then npm will just assume
  495. that it works on node.
  496. You can also use the "engines" field to specify which versions of npm
  497. are capable of properly installing your program. For example:
  498. { "engines" : { "npm" : "~1.0.20" } }
  499. Unless the user has set the `engine-strict` config flag, this
  500. field is advisory only and will only produce warnings when your package is installed as a dependency.
  501. ## engineStrict
  502. **This feature was removed in npm 3.0.0**
  503. Prior to npm 3.0.0, this feature was used to treat this package as if the
  504. user had set `engine-strict`. It is no longer used.
  505. ## os
  506. You can specify which operating systems your
  507. module will run on:
  508. "os" : [ "darwin", "linux" ]
  509. You can also blacklist instead of whitelist operating systems,
  510. just prepend the blacklisted os with a '!':
  511. "os" : [ "!win32" ]
  512. The host operating system is determined by `process.platform`
  513. It is allowed to both blacklist, and whitelist, although there isn't any
  514. good reason to do this.
  515. ## cpu
  516. If your code only runs on certain cpu architectures,
  517. you can specify which ones.
  518. "cpu" : [ "x64", "ia32" ]
  519. Like the `os` option, you can also blacklist architectures:
  520. "cpu" : [ "!arm", "!mips" ]
  521. The host architecture is determined by `process.arch`
  522. ## preferGlobal
  523. **DEPRECATED**
  524. This option used to trigger an npm warning, but it will no longer warn. It is
  525. purely there for informational purposes. It is now recommended that you install
  526. any binaries as local devDependencies wherever possible.
  527. ## private
  528. If you set `"private": true` in your package.json, then npm will refuse
  529. to publish it.
  530. This is a way to prevent accidental publication of private repositories. If
  531. you would like to ensure that a given package is only ever published to a
  532. specific registry (for example, an internal registry), then use the
  533. `publishConfig` dictionary described below to override the `registry` config
  534. param at publish-time.
  535. ## publishConfig
  536. This is a set of config values that will be used at publish-time. It's
  537. especially handy if you want to set the tag, registry or access, so that
  538. you can ensure that a given package is not tagged with "latest", published
  539. to the global public registry or that a scoped module is private by default.
  540. Any config values can be overridden, but only "tag", "registry" and "access"
  541. probably matter for the purposes of publishing.
  542. See `npm-config(7)` to see the list of config options that can be
  543. overridden.
  544. ## DEFAULT VALUES
  545. npm will default some values based on package contents.
  546. * `"scripts": {"start": "node server.js"}`
  547. If there is a `server.js` file in the root of your package, then npm
  548. will default the `start` command to `node server.js`.
  549. * `"scripts":{"install": "node-gyp rebuild"}`
  550. If there is a `binding.gyp` file in the root of your package and you have not defined an `install` or `preinstall` script, npm will
  551. default the `install` command to compile using node-gyp.
  552. * `"contributors": [...]`
  553. If there is an `AUTHORS` file in the root of your package, npm will
  554. treat each line as a `Name <email> (url)` format, where email and url
  555. are optional. Lines which start with a `#` or are blank, will be
  556. ignored.
  557. ## SEE ALSO
  558. * semver(7)
  559. * npm-init(1)
  560. * npm-version(1)
  561. * npm-config(1)
  562. * npm-config(7)
  563. * npm-help(1)
  564. * npm-install(1)
  565. * npm-publish(1)
  566. * npm-uninstall(1)