Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support `create-vite-plus`

Open
#2,602 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Domain
cli, tooling

Research direction

Start by inspecting how the existing vite-plus CLI exposes vp create and vp migrate, then review the proposed create-vite-plus wrapper and the ownership concern around create-vp. Done means users can run pnpm create vite-plus to create a project without the global vp binary, with the chosen packaging approach documented and working.

Written by the indexing model from the issue text.

Description

pending triage
Description

For users who don't use global vp binary, commands such as pnpm create vite-plus might be a more common way to create a project. This require create-vite-plus to be registered.

Suggested solution

create-vite-plus package is registered by @ Boshen, it can be a small wrapper of vite-plus local cli package, runs vp create internally, creates smallest impact.

One problem is create-vp is not owned by Vite+ team right now.

Alternative

Alternatively, we could move code about vp create and vp migrate to create-vite-plus, letting vite-plus depend on this package. This approach may bring some complexity, the main benefit is to avoid other Vite+ part be downloaded, which is not important enough.

Additional context

No response

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
5.8k
Forks
263
Avg merge
1d 3h
Merged PRs (30d)
147

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from voidzero-dev/vite-plus

All issues in voidzero-dev/vite-plus

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.