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.

96 lines
2.9 KiB

  1. npm-view(1) -- View registry info
  2. =================================
  3. ## SYNOPSIS
  4. npm view [<@scope>/]<name>[@<version>] [<field>[.<subfield>]...]
  5. aliases: info, show, v
  6. ## DESCRIPTION
  7. This command shows data about a package and prints it to the stream
  8. referenced by the `outfd` config, which defaults to stdout.
  9. To show the package registry entry for the `connect` package, you can do
  10. this:
  11. npm view connect
  12. The default version is "latest" if unspecified.
  13. Field names can be specified after the package descriptor.
  14. For example, to show the dependencies of the `ronn` package at version
  15. 0.3.5, you could do the following:
  16. npm view ronn@0.3.5 dependencies
  17. You can view child fields by separating them with a period.
  18. To view the git repository URL for the latest version of npm, you could
  19. do this:
  20. npm view npm repository.url
  21. This makes it easy to view information about a dependency with a bit of
  22. shell scripting. For example, to view all the data about the version of
  23. opts that ronn depends on, you can do this:
  24. npm view opts@$(npm view ronn dependencies.opts)
  25. For fields that are arrays, requesting a non-numeric field will return
  26. all of the values from the objects in the list. For example, to get all
  27. the contributor names for the "express" project, you can do this:
  28. npm view express contributors.email
  29. You may also use numeric indices in square braces to specifically select
  30. an item in an array field. To just get the email address of the first
  31. contributor in the list, you can do this:
  32. npm view express contributors[0].email
  33. Multiple fields may be specified, and will be printed one after another.
  34. For example, to get all the contributor names and email addresses, you
  35. can do this:
  36. npm view express contributors.name contributors.email
  37. "Person" fields are shown as a string if they would be shown as an
  38. object. So, for example, this will show the list of npm contributors in
  39. the shortened string format. (See `package.json(5)` for more on this.)
  40. npm view npm contributors
  41. If a version range is provided, then data will be printed for every
  42. matching version of the package. This will show which version of jsdom
  43. was required by each matching version of yui3:
  44. npm view yui3@'>0.5.4' dependencies.jsdom
  45. To show the `connect` package version history, you can do
  46. this:
  47. npm view connect versions
  48. ## OUTPUT
  49. If only a single string field for a single version is output, then it
  50. will not be colorized or quoted, so as to enable piping the output to
  51. another command. If the field is an object, it will be output as a JavaScript object literal.
  52. If the --json flag is given, the outputted fields will be JSON.
  53. If the version range matches multiple versions, than each printed value
  54. will be prefixed with the version it applies to.
  55. If multiple fields are requested, than each of them are prefixed with
  56. the field name.
  57. ## SEE ALSO
  58. * npm-search(1)
  59. * npm-registry(7)
  60. * npm-config(1)
  61. * npm-config(7)
  62. * npmrc(5)
  63. * npm-docs(1)