/var/lang/lib/node_modules/npm/man/man1
This explorer reads the filesystem of the server it runs on, so /workspace/user isn't present here. Browsing and the terminal still work against this server's own disk from /.
.TH "NPM-VIEW" "1" "February 2026" "NPM@11.11.0" "".SH "NAME"\fBnpm-view\fR - View registry info.SS "Synopsis".P.RS 2.nfnpm view \[lB]<package-spec>\[rB] \[lB]<field>\[lB].subfield\[rB]...\[rB] aliases: info, show, v.fi.RE.SS "Description".PThis command shows data about a package and prints it to stdout..PAs an example, to view information about the \fBconnect\fR package from the registry, you would run:.P.RS 2.nfnpm view connect.fi.RE.PThe default version is \fB"latest"\fR if unspecified..PField names can be specified after the package descriptor. For example, to show the dependencies of the \fBronn\fR package at version \fB0.3.5\fR, you could do the following:.P.RS 2.nfnpm view ronn@0.3.5 dependencies.fi.RE.PBy default, \fBnpm view\fR shows data about the current project context (by looking for a \fBpackage.json\fR). To show field data for the current project use a file path (i.e. \fB.\fR):.P.RS 2.nfnpm view . dependencies.fi.RE.PYou can view child fields by separating them with a period. To view the git repository URL for the latest version of \fBnpm\fR, you would run the following command:.P.RS 2.nfnpm view npm repository.url.fi.RE.PThis makes it easy to view information about a dependency with a bit of shell scripting. For example, to view all the data about the version of \fBopts\fR that \fBronn\fR depends on, you could write the following:.P.RS 2.nfnpm view opts@$(npm view ronn dependencies.opts).fi.RE.PFor fields that are arrays, requesting a non-numeric field will return all of the values from the objects in the list. For example, to get all the contributor email addresses for the \fBexpress\fR package, you would run:.P.RS 2.nfnpm view express contributors.email.fi.RE.PYou may also use numeric indices in square braces to specifically select an item in an array field. To just get the email address of the first contributor in the list, you can run:.P.RS 2.nfnpm view express contributors\[lB]0\[rB].email.fi.RE.PIf the field value you are querying for is a property of an object, you should run:.P.RS 2.nfnpm view express time'\[lB]4.8.0\[rB]'.fi.RE.PNote: When accessing object properties that contain special characters or numeric keys, you need to use quotes around the key name. For example, to get the publish time of a specific version:.P.RS 2.nfnpm view express "time\[lB]4.17.1\[rB]".fi.RE.PWithout quotes, the shell may interpret the square brackets as glob patterns, causing the command to fail. You can also access the time field for a specific version by specifying the version in the package descriptor:.P.RS 2.nfnpm view express@4.17.1 time.fi.RE.PThis will return all version-time pairs, but the context will be for that specific version..PMultiple fields may be specified, and will be printed one after another. For example, to get all the contributor names and email addresses, you can do this:.P.RS 2.nfnpm view express contributors.name contributors.email.fi.RE.P"Person" fields are shown as a string if they would be shown as an object. So, for example, this will show the list of \fBnpm\fR contributors in the shortened string format. (See \fB\[rs]fBpackage.json\[rs]fR\fR \fI\(la/configuring-npm/package-json\(ra\fR for more on this.).P.RS 2.nfnpm view npm contributors.fi.RE.PIf a version range is provided, then data will be printed for every matching version of the package. This will show which version of \fBjsdom\fR was required by each matching version of \fByui3\fR:.P.RS 2.nfnpm view yui3@'>0.5.4' dependencies.jsdom.fi.RE.PTo show the \fBconnect\fR package version history, you can do this:.P.RS 2.nfnpm view connect versions.fi.RE.SS "Field Access Patterns".PThe \fBnpm view\fR command supports different ways to access nested fields and array elements in package metadata. Understanding these patterns makes it easier to extract specific information..SS "Nested Object Fields".PUse dot notation to access nested object fields:.P.RS 2.nf# Access nested propertiesnpm view npm repository.urlnpm view express bugs.url.fi.RE.SS "Array Element Access".PFor arrays, use numeric indices in square brackets to access specific elements:.P.RS 2.nf# Get the first contributor's emailnpm view express contributors\[lB]0\[rB].email # Get the second maintainer's namenpm view express maintainers\[lB]1\[rB].name.fi.RE.SS "Object Property Access".PFor object properties (like accessing specific versions in the \fBtime\fR field), use bracket notation with the property name in quotes:.P.RS 2.nf# Get publish time for a specific versionnpm view express "time\[lB]4.17.1\[rB]" # Get dist-tagsnpm view express "dist-tags.latest".fi.RE.SS "Extracting Fields from Arrays".PRequest a non-numeric field on an array to get all values from objects in the list:.P.RS 2.nf# Get all contributor emailsnpm view express contributors.email # Get all contributor namesnpm view express contributors.name.fi.RE.SS "Configuration".SS "\fBjson\fR".RS 0.IP \(bu 4Default: false.IP \(bu 4Type: Boolean.RE 0 .PWhether or not to output JSON data, rather than the normal output..RS 0.IP \(bu 4In \fBnpm pkg set\fR it enables parsing set values with JSON.parse() before saving them to your \fBpackage.json\fR..RE 0 .PNot supported by all npm commands..SS "\fBworkspace\fR".RS 0.IP \(bu 4Default:.IP \(bu 4Type: String (can be set multiple times).RE 0 .PEnable running a command in the context of the configured workspaces of the current project while filtering by running only the workspaces defined by this configuration option..PValid values for the \fBworkspace\fR config are either:.RS 0.IP \(bu 4Workspace names.IP \(bu 4Path to a workspace directory.IP \(bu 4Path to a parent workspace directory (will result in selecting all workspaces within that folder).RE 0 .PWhen set for the \fBnpm init\fR command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project..PThis value is not exported to the environment for child processes..SS "\fBworkspaces\fR".RS 0.IP \(bu 4Default: null.IP \(bu 4Type: null or Boolean.RE 0 .PSet to true to run the command in the context of \fBall\fR configured workspaces..PExplicitly setting this to false will cause commands like \fBinstall\fR to ignore workspaces altogether. When not set explicitly:.RS 0.IP \(bu 4Commands that operate on the \fBnode_modules\fR tree (install, update, etc.) will link workspaces into the \fBnode_modules\fR folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, \fIunless\fR one or more workspaces are specified in the \fBworkspace\fR config..RE 0 .PThis value is not exported to the environment for child processes..SS "\fBinclude-workspace-root\fR".RS 0.IP \(bu 4Default: false.IP \(bu 4Type: Boolean.RE 0 .PInclude the workspace root when workspaces are enabled for a command..PWhen false, specifying individual workspaces via the \fBworkspace\fR config, or all workspaces via the \fBworkspaces\fR flag, will cause npm to operate only on the specified workspaces, and not on the root project..PThis value is not exported to the environment for child processes..SS "Output".PIf only a single string field for a single version is output, then it will not be colorized or quoted, to enable piping the output to another command. If the field is an object, it will be output as a JavaScript object literal..PIf the \fB--json\fR flag is given, the outputted fields will be JSON..PIf the version range matches multiple versions then each printed value will be prefixed with the version it applies to..PIf multiple fields are requested, then each of them is prefixed with the field name..SS "See Also".RS 0.IP \(bu 4npm help "package spec".IP \(bu 4npm help search.IP \(bu 4npm help registry.IP \(bu 4npm help config.IP \(bu 4npm help npmrc.IP \(bu 4npm help docs.RE 0