Zoltan Kochan
cb3f29bc0a
Part of pnpm/tasks#191. Wrong claims, fixed in the v12 docs and, where the same text is wrong for v11, in the v11 docs: - logout: drop the nonexistent --scope option. - patch: the edit dir is node_modules/.pnpm_patches/<name>@<version>; drop the "*" special case. - patch-commit: fix the ---patches-dir heading. - prefix: describe the real marker walk instead of "closest package.json". - setup: setup installs pnpm as a global package and writes pn/pnpx/pnx. - start, test: "run start" and "run test" are not aliases. - unlink: drop the system-wide and link --global wording. - unpublish: a package name is required; --otp has no env var; --registry wording. - update: --depth is dependency depth, not directory depth. - version: --tag-version-prefix defaults to the tagVersionPrefix setting. - view: the first argument is always the package. - why: drop --global and --only-projects; --exclude-peers has no effect; --prod includes optionalDependencies. - install: recursiveInstall spelling; replace the stale ci-info snippet. - v12 only: pack-app runtime default and builder download, pnx provisioning list and cmd.exe typo, tasks sample priority. Missing flags, settings, and error codes on the v12 pages: install (about twenty flags), lane, licenses, link, list, outdated, owner, pack-app path rules, pack, patch, patch-remove, peers, permissions, ping, pipeline, pm, pnx, prune, publish, rebuild, recursive, remove, repo, root, run, runtime, sbom, search, self-update, set-script, setup, shim, stage, star, start, store, tasks, team, test, token, unlink, unpublish, update, version, view, why, with. Stale history on the v12 pages: removed "Added in" markers older than v12 and rewrote "Since v11.x" and "In v11" sentences as current behavior (login, logout, licenses, link, outdated, patch, pnx, publish, runtime, sbom, self-update, setup, update, and others). Review follow-up: patch's default edit directory is named after the argument as typed (both versions); self-update installs the unscoped package only for pnpm 12 and newer; only --no-bail is restricted; npm_package_* covers name, version, config, engines and bin; prefix -g prints the parent of root -g; --optional no longer claims to override --no-optional.
46 lines
879 B
Markdown
46 lines
879 B
Markdown
---
|
|
id: view
|
|
title: pnpm view
|
|
---
|
|
|
|
Added in: v11.0.0
|
|
|
|
Aliases: `info`, `show`
|
|
|
|
View package metadata from the registry.
|
|
|
|
```sh
|
|
pnpm view [<pkg>]
|
|
pnpm view <pkg> [field...]
|
|
```
|
|
|
|
## Usage
|
|
|
|
Show all metadata for a package:
|
|
|
|
```sh
|
|
pnpm view express
|
|
```
|
|
|
|
Show a specific field:
|
|
|
|
```sh
|
|
pnpm view express version
|
|
pnpm view express dependencies
|
|
pnpm view express dist-tags
|
|
```
|
|
|
|
Show metadata for a specific version:
|
|
|
|
```sh
|
|
pnpm view express@4.18.0
|
|
```
|
|
|
|
When no package name is provided, `pnpm view` searches upward for the nearest project manifest (`package.json`, `package.yaml`, or `package.json5`) and uses its `name` field. If the manifest exists but has no `name`, the command fails. To select fields, name the package: the first argument is always the package, so `pnpm view version` looks up a package named `version`.
|
|
|
|
## Options
|
|
|
|
### --json
|
|
|
|
Output the metadata in JSON format.
|