Applications created by `vp create` come with eslint by default instead of oxlint

[wladpaiva]

Description

When we create an application using vp create vite or vp create next-app for example, they will come with eslint instead of oxlint. This is a problem on monorepos created by vite+ which already come with oxlint on their root.

Running pnpx @oxlint/migrate is not enough to migrate them completely

Suggested solution

since those templates are pretty much static I believe the vp create should do the migration automatically.

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.

[claude]

Analysis

Understanding the issue

When vp create vite or vp create next-app runs, it:

1. Delegates to the external scaffold tool (create-vite, create-next-app, etc.)
2. Calls rewriteMonorepoProject() (monorepo case) or rewriteStandaloneProject() (standalone case) to integrate the new project

The problem: neither rewriteMonorepoProject nor rewriteStandaloneProject calls migrateEslintToOxlint. They only handle things like package.json overrides, vite config merging, script rewrites, lint-staged config, etc. — but they do not remove ESLint and replace it with oxlint. ESLint artifacts from the external template remain intact.

Relevant files

• packages/cli/src/create/bin.ts:878 — calls rewriteMonorepoProject(fullPath, ...) after a remote template runs
• packages/cli/src/create/bin.ts:949 — calls rewriteStandaloneProject(fullPath, ...) for standalone
• packages/cli/src/migration/migrator.ts:201 — migrateEslintToOxlint() already exists and does everything needed (runs @oxlint/migrate, deletes ESLint configs, removes ESLint deps, rewrites scripts)
• packages/cli/src/migration/bin.ts:108 — migrateEslintToOxlint is called here during vp migrate, but not during vp create

Is this fixable?

Yes — the migration infrastructure is already fully in place. The fix is to call migrateEslintToOxlint in the vp create flow, right after the external template is applied.

Implementation plan

1. packages/cli/src/create/bin.ts — import detectEslintProject and migrateEslintToOxlint from the migration module

2. Monorepo case (around line 878): after rewriteMonorepoProject(fullPath, ...), add:

   updateCreateProgress('Migrating ESLint to oxlint');
   const eslintProject = detectEslintProject(fullPath);
   if (eslintProject.hasDependency && eslintProject.configFile) {
     await migrateEslintToOxlint(fullPath, false /* non-interactive */, eslintProject.configFile);
   }

3. Standalone case (around line 949): same pattern after rewriteStandaloneProject(fullPath, ...).

4. Add snap tests to cover the new behavior — e.g., a fixture that simulates a newly-created Vite project with ESLint config and verifies it gets migrated to oxlint during vp create.

Potential concerns

• migrateEslintToOxlint runs @oxlint/migrate as an external process — this is fine since vp create is already running other async/external steps (install, fmt)
• For templates that do not include ESLint (e.g., hypothetical future templates), the detectEslintProject check guards against no-ops
• Some external templates may use non-standard ESLint config locations; the existing detection logic in detectEslintProject already handles this
• The @oxlint/migrate tool may not cover 100% of cases — but the same is true during vp migrate, and any gaps can be addressed incrementally

[mfulton26]

I agree, some viteplus specific templates may be helpful, especially when using a monorepo so that .vscode and other things are not duplicated and the package.json#/scripts are already configured to use vp.

[fengmk2]

#1434