Zoltan KochanandClaude Opus 5.5
6f95957063
* docs: lint prose with Vale Add Vale with an in-repo style, .vale/styles/pnpm, that turns the writing rules in AGENTS.md and the Google developer documentation style guide into lint rules. The stock Vale packages (Google, Microsoft, RedHat, write-good) were too noisy to block on, for example 1,300 passive-voice hits in the v12 docs alone, so the rules are written for this repo, following the GitLab model. Each one links the guideline it enforces. Levels: - error, fails CI: dashes, plain-word substitutions, condescending words, "please", "note that", hedges, puffery, optional plurals, exclamation marks, ellipses, curly quotes, generic link text, product spellings, sentence-case headings, repeated words, double spaces, implementation history in comments; in changesets, bold or italic emphasis, internal names and release-line names. - warning: future tense, sentences over 30 words, "instead of" and "so that" tails in changesets. - suggestion: passive voice. .vale.ini scopes the rules. Docs get every rule. Contributor Markdown and code comments keep dashes and headings as warnings until their roughly 8,100 em dashes are rewritten. Released changesets stay in .changeset/ and are not rewritten, so lint-prose.mjs lints only the changesets added since PROSE_BASE (the PR base in CI). The prose workflow installs a pinned, checksum-verified Vale release and runs `pnpm lint:prose`. The rest of this change rewrites the existing docs, READMEs, contributor Markdown, and code comments to pass the error-level rules. Only prose and comment text changed. Renamed headings keep their anchors. Spelling stays with cspell, which checks identifiers that Vale does not see. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * docs: keep prose lint from flattening meaning --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
1.1 KiB
1.1 KiB
id, title
| id | title |
|---|---|
| repo | pnpm repo |
Added in: v11.3.0
Opens the URL of a package's repository in the browser.
pnpm repo [<pkg> ...]
With no arguments, opens the repository of the current project (read from the repository field of package.json).
With one or more package names, fetches each package's metadata from the registry and opens its repository URL.
The repository URL is normalized to its web equivalent, e.g. git+ssh://git@github.com/foo/bar.git opens as https://github.com/foo/bar. When the repository field includes a directory, the URL points at that subdirectory inside the repo.
Examples
# Open the repo of the current project
pnpm repo
# Open the repo of a package on the registry
pnpm repo lodash
# Open multiple repos at once
pnpm repo react react-dom
Options
--registry <url>
The registry from which to fetch package metadata when an explicit package name is given. Per-scope and named registries (configured via registries and namedRegistries) are respected.