feat: support project-aware global shims for vp-installed global CLIs
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with the pnpm project-aware global bins reference and trace how vp i -g currently installs global CLIs. Define the project context, resolution behavior, workspace-root handling, and cross-platform shim expectations before identifying implementation points. Done means globally installed CLIs behave as normal executables while resolving project context appropriately.
Written by the indexing model from the issue text.
Description
Summary
Add support in vite-plus for project-aware global shims for CLIs installed via vp i -g.
pnpm reference
pnpm documents project-aware global bins here:
https://pnpm.io/global-packages#project-aware-global-bins
From the docs, the relevant behavior is:
- globally installed packages are isolated from each other
- bin shims are generated in the global bin directory
- those shims point into the appropriate install group
- the invoked CLI can operate with awareness of the current project context
What we want for vite-plus
For CLIs installed via vp i -g:
- global shims should be available as normal executables
- when invoked inside a project, the shim/runtime should resolve against the current project context where appropriate
- the behavior should feel similar to local project bins, but for globally installed tooling
Open questions
- Should vite-plus mirror pnpm's approach closely, or adapt it to vp's own installation/runtime model?
- What project context needs to be discovered at execution time?
- Are there edge cases around resolution, workspace roots, or cross-platform shim generation?
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 267
- Avg merge
- 20h 7m
- Merged PRs (30d)
- 139
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from voidzero-dev/vite-plus
-
pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
voidzero-dev/vite-plus#2854 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
voidzero-dev/vite-plus#2849 ·
Maintainers usually reply within 1 day
-
pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
voidzero-dev/vite-plus#2801 · 1 reaction ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
voidzero-dev/vite-plus#2097 · 10 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
pending triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
voidzero-dev/vite-plus#2866 ·
Maintainers usually reply within 1 day
All issues in voidzero-dev/vite-plus
Similar issues
-
Change output crossing a compactsize boundary leaves the fee slightly below the requested feerateOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
bitcoindevkit/bdk_wallet#578 ·
Maintainers usually reply within 8 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
521xueweihan/HelloGitHub#3832 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
canonical/opentelemetry-collector-operator#409 ·
Maintainers usually reply within 1 day