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.

154 lines
4.1 KiB

  1. .TH "NPM\-OUTDATED" "1" "August 2018" "" ""
  2. .SH "NAME"
  3. \fBnpm-outdated\fR \- Check for outdated packages
  4. .SH SYNOPSIS
  5. .P
  6. .RS 2
  7. .nf
  8. npm outdated [[<@scope>/]<pkg> \.\.\.]
  9. .fi
  10. .RE
  11. .SH DESCRIPTION
  12. .P
  13. This command will check the registry to see if any (or, specific) installed
  14. packages are currently outdated\.
  15. .P
  16. In the output:
  17. .RS 0
  18. .IP \(bu 2
  19. \fBwanted\fP is the maximum version of the package that satisfies the semver
  20. range specified in \fBpackage\.json\fP\|\. If there's no available semver range (i\.e\.
  21. you're running \fBnpm outdated \-\-global\fP, or the package isn't included in
  22. \fBpackage\.json\fP), then \fBwanted\fP shows the currently\-installed version\.
  23. .IP \(bu 2
  24. \fBlatest\fP is the version of the package tagged as latest in the registry\.
  25. Running \fBnpm publish\fP with no special configuration will publish the package
  26. with a dist\-tag of \fBlatest\fP\|\. This may or may not be the maximum version of
  27. the package, or the most\-recently published version of the package, depending
  28. on how the package's developer manages the latest npm help dist\-tag\.
  29. .IP \(bu 2
  30. \fBlocation\fP is where in the dependency tree the package is located\. Note that
  31. \fBnpm outdated\fP defaults to a depth of 0, so unless you override that, you'll
  32. always be seeing only top\-level dependencies that are outdated\.
  33. .IP \(bu 2
  34. \fBpackage type\fP (when using \fB\-\-long\fP / \fB\-l\fP) tells you whether this package is
  35. a \fBdependency\fP or a \fBdevDependency\fP\|\. Packages not included in \fBpackage\.json\fP
  36. are always marked \fBdependencies\fP\|\.
  37. .IP \(bu 2
  38. Red means there's a newer version matching your semver requirements, so you should update now\.
  39. .IP \(bu 2
  40. Yellow indicates that there's a newer version above your semver requirements (usually new major, or new 0\.x minor) so proceed with caution\.
  41. .RE
  42. .SS An example
  43. .P
  44. .RS 2
  45. .nf
  46. $ npm outdated
  47. Package Current Wanted Latest Location
  48. glob 5\.0\.15 5\.0\.15 6\.0\.1 test\-outdated\-output
  49. nothingness 0\.0\.3 git git test\-outdated\-output
  50. npm 3\.5\.1 3\.5\.2 3\.5\.1 test\-outdated\-output
  51. local\-dev 0\.0\.3 linked linked test\-outdated\-output
  52. once 1\.3\.2 1\.3\.3 1\.3\.3 test\-outdated\-output
  53. .fi
  54. .RE
  55. .P
  56. With these \fBdependencies\fP:
  57. .P
  58. .RS 2
  59. .nf
  60. {
  61. "glob": "^5\.0\.15",
  62. "nothingness": "github:othiym23/nothingness#master",
  63. "npm": "^3\.5\.1",
  64. "once": "^1\.3\.1"
  65. }
  66. .fi
  67. .RE
  68. .P
  69. A few things to note:
  70. .RS 0
  71. .IP \(bu 2
  72. \fBglob\fP requires \fB^5\fP, which prevents npm from installing \fBglob@6\fP, which is
  73. outside the semver range\.
  74. .IP \(bu 2
  75. Git dependencies will always be reinstalled, because of how they're specified\.
  76. The installed committish might satisfy the dependency specifier (if it's
  77. something immutable, like a commit SHA), or it might not, so \fBnpm outdated\fP and
  78. \fBnpm update\fP have to fetch Git repos to check\. This is why currently doing a
  79. reinstall of a Git dependency always forces a new clone and install\.
  80. .IP \(bu 2
  81. \fBis marked as "wanted", but "latest" is\fP\fBbecause npm
  82. uses dist\-tags to manage its\fPlatest\fBand\fPnext\fBrelease channels\.\fPnpm update\fBwill install the _newest_ version, but\fPnpm install npm\fB(with no semver range)
  83. will install whatever's tagged as\fPlatest`\.
  84. .IP \(bu 2
  85. \fBonce\fP is just plain out of date\. Reinstalling \fBnode_modules\fP from scratch or
  86. running \fBnpm update\fP will bring it up to spec\.
  87. .RE
  88. .SH CONFIGURATION
  89. .SS json
  90. .RS 0
  91. .IP \(bu 2
  92. Default: false
  93. .IP \(bu 2
  94. Type: Boolean
  95. .RE
  96. .P
  97. Show information in JSON format\.
  98. .SS long
  99. .RS 0
  100. .IP \(bu 2
  101. Default: false
  102. .IP \(bu 2
  103. Type: Boolean
  104. .RE
  105. .P
  106. Show extended information\.
  107. .SS parseable
  108. .RS 0
  109. .IP \(bu 2
  110. Default: false
  111. .IP \(bu 2
  112. Type: Boolean
  113. .RE
  114. .P
  115. Show parseable output instead of tree view\.
  116. .SS global
  117. .RS 0
  118. .IP \(bu 2
  119. Default: false
  120. .IP \(bu 2
  121. Type: Boolean
  122. .RE
  123. .P
  124. Check packages in the global install prefix instead of in the current
  125. project\.
  126. .SS depth
  127. .RS 0
  128. .IP \(bu 2
  129. Default: 0
  130. .IP \(bu 2
  131. Type: Int
  132. .RE
  133. .P
  134. Max depth for checking dependency tree\.
  135. .SH SEE ALSO
  136. .RS 0
  137. .IP \(bu 2
  138. npm help update
  139. .IP \(bu 2
  140. npm help dist\-tag
  141. .IP \(bu 2
  142. npm help 7 registry
  143. .IP \(bu 2
  144. npm help 5 folders
  145. .RE