vp create with non-global package manager

[cavivie]

Description

vp create works perfectly when I have a global package manager. Conversely, if I try to create a project using vp create and then install a package manager for per-project mode using methods like mise, it fails.

The experience would be much better if I could start working without a pre-installed package manager, as I've always installed package managers per-project mode without a global package manager (except for npm).

Suggested solution

1. During vp create when selecting a package manager:

• It may check if the user has a global package manager, and provides their selections.
• If no other global package manager exists, it will fall back to the npm package manager.

2. When vp acts as a package manager:

• It provides a padding for vp, providing the functionality to download a package manager.
• vp itself is a package manager (requiring vp to implement functions similar to npm, pnpm, yarn, etc.).

Alternative

No response

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.

[fengmk2]

Because vp itself can provide multiple package managers, you can choose one that you are comfortable using. Vite+ has no plans to fully implement a package manager.

[cavivie]

@fengmk2 I don't think the issue is to let vp implement a package manager. The issue is that the current detection of vp package management seems to be unable to detect the package manager installed in some ways. vp can detect the global package management installed by brew/apt/winget. Why can't package managers installed by mise be detected? Se and other project-level package managers installed? I just stated my problem, and then provided a plan (which may not be adopted) to avoid such phenomena: either improve the way vp detects the package manager, or provide the functions of the package manager itself, otherwise I still can't use other packages except the global package manager installation. Manager, because vp currently seems to ignore the high-priority package manager in the PATH environment. Please re-open this issue!

[fengmk2]

Currently, vp requires the use of the packageManager field to set the type and version of the package manager used in the project. This is a strict requirement, so even if mise has a global pnpm installed, it will not be used by vp.