Repository navigation
Support pnpm catalog #1835
Description
Description
In current Vite+, when running vp add vue with pnpm catalogs configured in pnpm-workspace.yaml, it totally ignores the catalog and add the package with it version directly in package.json.
Since pnpm catalogs feature provide a lot of benefit for packages management (Anthony Fu wrote a blog about it), it will be great if VIte+ does support it.
Suggested solution
-
This feature can be toggle by a config in
vite.config.ts:pnpm.catalog: booleanor an env var likeVP_CATALOG=boolean. -
When running
vp addand Vite+ detects a workspace that use pnpm catalog: instead of adding packages with pinned versions, it writescatalog:references intopackage.jsonand updates the workspace catalog:
# Given pnpm-workspace.yaml with:
# catalogs:
# prod:
# react: ^18.3.0
vp add react
# → detects react in "prod" catalog
# → writes "react": "catalog:prod" to package.json
# → runs vp install
vp add lodash
# → lodash not in any catalog
# → prompts to select a catalog (or skip)
# → fetches latest version, updates pnpm-workspace.yaml
# → writes "lodash": "catalog:prod" to package.json
# → runs vp installAlternative
No response
Additional context
This feature is inspired by ni
Validations
- Read the Contributing Guidelines.
- Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
- Check that there isn't already an issue requesting the same feature.
Activity
jong-kyung commentedon Jun 15, 2026
Thanks for the request!
Vite+ already forwards pnpm catalog flags:
vp add react --save-catalogvp add react --save-catalog-name prodAnd when
catalogMode: preferis configured, plainvp addfollows pnpm’s native behavior for the default catalog.tobynguyen27 commentedon Jun 15, 2026
It'd be nice if we added an interact TUI:
When execute
vp add react. It will show a prompt that asks user which catalog should this package added to or creating a new catalog (this TUI is only for workspace which is using name catalogs)