mirror of
https://github.com/pnpm/pnpm.git
synced 2026-04-13 11:39:44 -04:00
f1dbe4edf8
* feat!: stop falling back to npm CLI * chore: update pnpm-lock.yaml * fix: resolve conflicts * revert: keep falling back to npm CLI for config get/set Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: lint errors in notImplemented.ts Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * chore: update changeset description Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * feat: suggest using npm CLI in not-implemented error message Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: address review comments - Check combined stdout+stderr in test for ERR_PNPM_NOT_IMPLEMENTED - Skip unknown options validation for not-implemented commands - Mention aliases (s, se, v) in changeset Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
530 B
530 B
pnpm
| pnpm |
|---|
| major |
Stop falling back to the npm CLI. Commands that were previously passed through to npm (access, adduser, bugs, deprecate, dist-tag, docs, edit, find, home, info, issues, login, logout, owner, ping, prefix, profile, pkg, repo, search, set-script, show, star, stars, team, token, unpublish, unstar, version, view, whoami, xmas) and their aliases (s, se, v) now throw a "not implemented" error with a suggestion to use the npm CLI directly.