Skip to content

fix(pm): allow registry commands to work outside a project#1151

Merged
graphite-app[bot] merged 1 commit intomainfrom
fix-1108
Mar 27, 2026
Merged

fix(pm): allow registry commands to work outside a project#1151
graphite-app[bot] merged 1 commit intomainfrom
fix-1108

Conversation

@fengmk2
Copy link
Member

@fengmk2 fengmk2 commented Mar 26, 2026

Commands like vp info, vp pm search, vp pm ping, and other
registry/auth operations no longer require a package.json. When no
project is found, these standalone commands fall back to a default
npm package manager instance.

Project-dependent commands (prune, pack, list, publish, rebuild,
fund, audit) still require a package.json and show the existing
"No package.json found." error.

Closes #1108

@fengmk2 fengmk2 self-assigned this Mar 26, 2026
Copy link
Member Author

fengmk2 commented Mar 26, 2026


How to use the Graphite Merge Queue

Add the label auto-merge to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@fengmk2 fengmk2 changed the base branch from auto-remove-esModuleInterop-false-on-migrate to graphite-base/1151 March 26, 2026 12:35
@fengmk2 fengmk2 force-pushed the graphite-base/1151 branch from 6749b17 to 5f52b6c Compare March 26, 2026 12:35
@fengmk2 fengmk2 changed the base branch from graphite-base/1151 to main March 26, 2026 12:35
@fengmk2 fengmk2 marked this pull request as ready for review March 26, 2026 12:35
@fengmk2 fengmk2 requested review from branchseer and cpojer March 26, 2026 12:36
@graphite-app
Copy link

graphite-app bot commented Mar 27, 2026

Merge activity

Commands like `vp info`, `vp pm search`, `vp pm ping`, and other
registry/auth operations no longer require a package.json. When no
project is found, these standalone commands fall back to a default
npm package manager instance.

Project-dependent commands (prune, pack, list, publish, rebuild,
fund, audit) still require a package.json and show the existing
"No package.json found." error.

Closes #1108
@netlify
Copy link

netlify bot commented Mar 27, 2026

Deploy Preview for viteplus-preview canceled.

Name Link
🔨 Latest commit 826142d
🔍 Latest deploy log https://app.netlify.com/projects/viteplus-preview/deploys/69c5e9f365346e0008d99512

@graphite-app graphite-app bot merged commit 826142d into main Mar 27, 2026
24 checks passed
@graphite-app graphite-app bot deleted the fix-1108 branch March 27, 2026 02:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

vp info vite versions outside of a project fails with "No package.json found."

3 participants