Skip to content

Do not update package.json when running vpr #2374

Description

@BlankParticle

Description

Running a script with vpr can add package manager metadata to package.json.

This is unexpected when I only want to run a script, especially in someone else’s repository. Coding agents also freak out with this behaviour, Vite+ edits package.json, the agent reverts the unexpected change, and Vite+ adds it again on the next vpr command.

Vite+ should not automatically edit files as side effects.

Suggested solution

Do not add packageManager or devEngines.packageManager metadata as a side effect of running vpr/vp run.

Pinning a package manager should require an explicit user action, such as a dedicated vp pm pin command.

Alternative

No response

Additional context

I want to fix this if we go with this proposal 🫡

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.

Activity

  1. liangmiQwQ commented on Aug 8, 2026

    @liangmiQwQ
    Collaborator

    @BlankParticle Hello, thanks for reporting that!

    When I dig into it, I found this is actually caused by a larger, more fundamental issue (Vite+ cannot ensure the package manager is in the PATH, #2375). I noticed before and recently submit an issue and am working on a refactoring.

    I'm not sure if it will be more thorough or easier to handle it during the refactoring. Anyway, I will change the issue type to Bug and share more information here :)

  2. changed the issue type fromtoon Aug 8, 2026
  3. BlankParticle commented on Aug 8, 2026

    @BlankParticle
    ContributorAuthor

    thanks, if you are working on this while refactoring that would be great, I can give more feedback on the behaviour I would like once you have more info/have a better version implemented

  4. self-assigned this
    on Aug 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

Priority

None yet

Effort

None yet

Target date

None yet

Start date

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions