Aid migration by running local package.json scripts lint command instead

[will-stone]

Description

I see the migration to Vite+ being piecemeal. Currently most projects have a "lint" package.json script set up. It's very easy to forget run and use vp lint. This then runs a different lint to the one that the user is expecting.

Suggested solution

How about defaulting to running the "lint" script in package.json, if found and no lint entry in vite.config.ts, with a warning at the top:

> vp lint

Detected "lint" script in package.json. Running this script instead of Vite's default linter...

Then, if there's both a "lint" script and a lint entry in vite.config.ts, it can continue to ignore the package.json script but with a warning...

> vp lint

Detected both a "lint" package.json script and Vite "lint" config. Use `vite run lint` to run
the "lint" package.json script. Using Vite's linter...

Alternative

No response

Additional context

Thanks for considering! 🙂

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]

This is the same kind of developer experience issue as #770 @cpojer do you need to take another look?