Warn for unsupported package manager flags instead of silently ignoring
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start at the vp pm package-manager compatibility layer and trace how supported and unsupported flags are handled, comparing existing warnings with flags that are silently ignored. Done means unsupported flags consistently produce warnings without changing the behavior of supported flags; the issue does not identify specific files or tests to run.
Written by the indexing model from the issue text.
Description
Description
vp pm is a package manager compatibility layer, since different underlying package managers can have some small differences. It is common to meet cases that there is a --abc flag can be passed to Xpm, but not to Ypm.
The current Vite+'s behavior is not united. It sometimes prints a warning (e.g. --fix-lockfile, --offline, --latest) but it also silently ignores some of them (e.g. --workspace, --save-catalog), which may make users confused.
Suggested solution
We are supposed to show warnings for these cases instead of silently ignoring, it can help users or agents know how to use the package manager correctly.
As for the implementation, I think checking and writing all of them by hand can be a little bit troublesome. We'd better to find a way to check them unitedly or use Rust's language feature like macro or Drop trait to reduce complex works.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 263
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 148
Contributor 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
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
voidzero-dev/vite-plus#2097 · 10 comments · 2 reactions ·
-
pending triage
Difficulty 5/5 Over a week Newbie friendliness 45/100
voidzero-dev/vite-plus#2781 · 2 reactions ·
-
enhancement
voidzero-dev/vite-plus#2766 · 4 comments · 1 reaction · 1 assignee ·
-
enhancement
voidzero-dev/vite-plus#2764 · 3 comments · 1 assignee ·
-
pending triage
Difficulty 3/5 1-2 days Newbie friendliness 68/100
voidzero-dev/vite-plus#2735 ·
All issues in voidzero-dev/vite-plus
Similar issues
-
Browser (wasm) relay client cannot connect to relays whose URL has a trailing-dot FQDN hostname Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
n0-computer/iroh#4550 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
paritytech/zombienet-sdk#591 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
farion1231/cc-switch#7638 · 1 comment ·
-
onnx-ir re-exports ModelProto and GraphProto but not NodeProto, AttributeProto and AttributeType Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100