Skip the `vpr` hint when the script runs the same built-in
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
Research direction
Start with packages/cli/binding/src/cli/script_note.rs, especially has_package_json_script, and read its existing tests and callers. Run the relevant CLI tests, then verify the hint is skipped for an exact vp <same-command> script but remains when the script adds arguments, such as vp test --coverage.
Written by the indexing model from the issue text.
Description
Description
The hint from #2243 shows even when the matching script just runs the same built-in:
{
"scripts": {
"test": "vp test"
}
}
$ vp test
note: You are running `vp test` as a Vite+ built-in command. If you meant to run the test npm script, use `vpr test` instead.
vp test and vpr test do the same thing here, so the note is noise.
vp create generates "dev": "vp dev" (snapshot), so new projects show the note on vp dev.
The only way to avoid the note is to rename the script (e.g. test → test:unit).
Suggested solution
has_package_json_script already reads the script value (it checks is_string), so this only changes the condition: skip the hint when the script is exactly vp <same-command>. Keep it if the script adds arguments (e.g. vp test --coverage), since the two commands then differ.
Alternative
Add an option to turn off the hint.
Additional context
Reproduced on Vite+ v1.0.0. Source links point to main (1d549b9).
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.
- Dominant language
- Rust
- Stars
- 6k
- Forks
- 271
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 172
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
-
`~/.vite-plus/env` costs 85-315 ms per shell start on long PATHs (super-linear `${var#*pattern}` in the dedupe loop)Possibly taken @jonatankruszewski claimed this today. Opencontribution welcome
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
voidzero-dev/vite-plus#2898 · 3 reactions ·
Maintainers usually reply within 1 day
-
pending triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
voidzero-dev/vite-plus#2882 · 2 comments ·
Maintainers usually reply within 1 day
-
documentation pending triage
Difficulty 1/5 Under an hour Newbie friendliness 78/100
voidzero-dev/vite-plus#2875 · 4 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
voidzero-dev/vite-plus#2849 · 1 comment · 1 assignee ·
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
All issues in voidzero-dev/vite-plus
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 5 days
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
ktuner keeps a stale ledger path and can never restore that entryPossibly taken @Frun1na claimed this today. Opencomponent:ktuner
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
agentic-os-org/ANOLISA#6483 · 1 comment ·
Maintainers usually reply within 1 day
-
[Resource]: snapbackOpenresource-submission validation-passed
Difficulty 1/5 Under an hour Newbie friendliness 85/100
hesreallyhim/awesome-claude-code#3095 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day