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.

90 lines
2.7 KiB

  1. npmrc(5) -- The npm config files
  2. ================================
  3. ## DESCRIPTION
  4. npm gets its config settings from the command line, environment
  5. variables, and `npmrc` files.
  6. The `npm config` command can be used to update and edit the contents
  7. of the user and global npmrc files.
  8. For a list of available configuration options, see npm-config(7).
  9. ## FILES
  10. The four relevant files are:
  11. * per-project config file (/path/to/my/project/.npmrc)
  12. * per-user config file (~/.npmrc)
  13. * global config file ($PREFIX/etc/npmrc)
  14. * npm builtin config file (/path/to/npm/npmrc)
  15. All npm config files are an ini-formatted list of `key = value`
  16. parameters. Environment variables can be replaced using
  17. `${VARIABLE_NAME}`. For example:
  18. prefix = ${HOME}/.npm-packages
  19. Each of these files is loaded, and config options are resolved in
  20. priority order. For example, a setting in the userconfig file would
  21. override the setting in the globalconfig file.
  22. Array values are specified by adding "[]" after the key name. For
  23. example:
  24. key[] = "first value"
  25. key[] = "second value"
  26. #### Comments
  27. Lines in `.npmrc` files are interpreted as comments when they begin with a `;` or `#` character. `.npmrc` files are parsed by [npm/ini](https://github.com/npm/ini), which specifies this comment syntax.
  28. For example:
  29. # last modified: 01 Jan 2016
  30. ; Set a new registry for a scoped package
  31. @myscope:registry=https://mycustomregistry.example.org
  32. ### Per-project config file
  33. When working locally in a project, a `.npmrc` file in the root of the
  34. project (ie, a sibling of `node_modules` and `package.json`) will set
  35. config values specific to this project.
  36. Note that this only applies to the root of the project that you're
  37. running npm in. It has no effect when your module is published. For
  38. example, you can't publish a module that forces itself to install
  39. globally, or in a different location.
  40. Additionally, this file is not read in global mode, such as when running
  41. `npm install -g`.
  42. ### Per-user config file
  43. `$HOME/.npmrc` (or the `userconfig` param, if set in the environment
  44. or on the command line)
  45. ### Global config file
  46. `$PREFIX/etc/npmrc` (or the `globalconfig` param, if set above):
  47. This file is an ini-file formatted list of `key = value` parameters.
  48. Environment variables can be replaced as above.
  49. ### Built-in config file
  50. `path/to/npm/itself/npmrc`
  51. This is an unchangeable "builtin" configuration file that npm keeps
  52. consistent across updates. Set fields in here using the `./configure`
  53. script that comes with npm. This is primarily for distribution
  54. maintainers to override default configs in a standard and consistent
  55. manner.
  56. ## SEE ALSO
  57. * npm-folders(5)
  58. * npm-config(1)
  59. * npm-config(7)
  60. * package.json(5)
  61. * npm(1)