Disable VSCode settings generation in monorepo mode

[aulikhin]

Description

When generating a new app or library in monorepo mode, Vite+ currently prompts Which editor are you using? and creates .vscode settings for the generated project.

In a monorepo setup, editor configuration is usually managed at the workspace root, so generating .vscode settings for each new package/app may introduce unnecessary or conflicting configuration files.

Suggested solution

Individual packages/apps should remain editor-agnostic. Automatically skip promoting and generating .vscode settings in monorepo projects

Alternative

No response

Additional context

Steps to reproduce

1. vp create vite:monorepo --no-interactive
2. cd your-app && vp create

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 running vp create inside an existing monorepo (e.g., adding a new package), the CLI still prompts "Which editor are you using?" and writes .vscode settings into the new package directory. In a monorepo, editor configuration belongs at the workspace root, not in each individual package.

---

Relevant code

packages/cli/src/create/bin.ts

Editor prompt (lines 626–636) — runs regardless of isMonorepo:

const existingEditor =
  options.editor || !options.interactive
    ? undefined
    : detectExistingEditor(workspaceInfoOptional.rootDir);
selectedEditor =
  existingEditor ??
  (await selectEditor({ interactive: options.interactive, editor: options.editor, ... }));

Editor config written to the package directory in both code paths (lines 829–836), even when isMonorepo is true:

await writeEditorConfigs({
  projectRoot: fullPath,   // <-- package dir, not workspace root
  editorId: selectedEditor,
  ...
});

Compare with how agent instructions already handle this correctly (line 819):

const agentInstructionsRoot = isMonorepo ? workspaceInfo.rootDir : fullPath;

The isMonorepo variable is already available at line 408 and is used to guard other behavior (e.g., git hooks are skipped for monorepos at line 638).

---

Verdict: Fixable — low complexity

---

Implementation plan

1. Skip the editor prompt when already inside a monorepo (packages/cli/src/create/bin.ts, around line 626):

   const existingEditor =
     options.editor || !options.interactive || isMonorepo   // <-- add isMonorepo check
       ? undefined
       : detectExistingEditor(workspaceInfoOptional.rootDir);
   selectedEditor =
     existingEditor ??
     (await selectEditor({ interactive: options.interactive, editor: options.editor, ... }));

   When isMonorepo is true, existingEditor becomes undefined and selectEditor will be called with editor: undefined, interactive: .... However selectEditor with no interactive input will still prompt if interactive is true — so we need to also handle the isMonorepo case inside selectEditor, or simply set selectedEditor = undefined and skip writeEditorConfigs entirely.

   Simpler approach: gate both the prompt and the write on !isMonorepo:

   // Skip editor selection and config writing when inside a monorepo
   if (!isMonorepo) {
     const existingEditor = ...;
     selectedEditor = existingEditor ?? (await selectEditor(...));
   }

2. Skip writeEditorConfigs for individual packages in an existing monorepo (lines 829–836):

   if (!isMonorepo) {
     updateCreateProgress('Writing editor configs');
     pauseCreateProgress();
     await writeEditorConfigs({
       projectRoot: fullPath,
       editorId: selectedEditor,
       interactive: options.interactive,
       silent: compactOutput,
     });
     resumeCreateProgress();
   }

3. Note: The writeEditorConfigs call at lines 740–748 (for the monorepo template itself — i.e., creating a brand-new monorepo from scratch) should be kept as-is. Writing .vscode to the root of a freshly created monorepo is appropriate.

4. Update snap tests in packages/cli/snap-tests/ and packages/cli/snap-tests-global/ — any test that exercises vp create inside an existing monorepo will need its snap.txt regenerated to remove the editor prompt/output.

---

Potential concerns

• If a user wants to add editor config to a specific package for some reason, they lose the ability to do so via vp create. This seems acceptable given the issue's stated goal.
• The --editor CLI flag is currently a no-op in monorepo mode after this change. A future enhancement could support --editor to explicitly opt-in to writing editor configs even in monorepo mode, but that is out of scope for this fix.