Create Vite Help

[Kaizen-BT]

Hi,

I saw from the help docs from the cli that --no-immediate is not part of the flags in the help docs of the cli:

> npx
> "create-vite" --help

Usage: create-vite [OPTION]... [DIRECTORY]

Create a new Vite project in JavaScript or TypeScript.
When running in TTY, the CLI will start in interactive mode.

Options:
  -t, --template NAME                   use a specific template
  -i, --immediate                       install dependencies and start dev
  --rolldown / --no-rolldown            use / do not use rolldown-vite (Experimental)
  --interactive / --no-interactive      force interactive / non-interactive mode

Available templates:
vanilla-ts          vanilla
vue-ts              vue
react-ts            react
react-compiler-ts   react-compiler
react-swc-ts        react-swc
preact-ts           preact
lit-ts              lit
svelte-ts           svelte
solid-ts            solid
qwik-ts             qwik

However, passing --no-immediate is possible and will do the opposite of --immediate as seen below:

> npx
> "create-vite" renderer --no-immediate

│
◇  Select a framework:
│  React
│
◇  Select a variant:
│  TypeScript + SWC
│
◇  Use rolldown-vite (Experimental)?:
│  No
│
◇  Scaffolding project in /home/alias-ktc/Learning-Projects/renderer...
│
└  Done. Now run:

  cd renderer
  npm install
  npm run dev

Kindly, is there a reason --no-immediate wasn't documented? Are there any side-effects to the above ? Thank you.

[tt-a1i]

This is standard CLI behavior for boolean flags - when a flag like --immediate exists, most CLI parsers automatically support its negation --no-immediate.

The help docs typically only show the "positive" form since the negation is implied. In this case:

• --immediate = install deps and start dev
• --no-immediate (or omitting the flag) = just scaffold, don't auto-install

There are no side effects - --no-immediate is essentially the default behavior, so passing it explicitly just ensures you get the scaffold-only mode even if the default changes in the future.

That said, documenting both forms could reduce confusion. You could open a small PR to add --no-immediate to the help output if you think it would help others.

[Kaizen-BT]

Thank you for the quick response I'll do so.

[masonearl]

Great observation! This is actually a standard behavior in many CLI tools that use boolean flags.

Why --no-immediate Works

Most CLI parsing libraries (including the ones used by create-vite) automatically generate negated versions of boolean flags. When you define --immediate, the parser automatically supports:

• --immediate → sets the value to true
• --no-immediate → sets the value to false

This is part of the Commander.js convention that Vite's CLI likely follows.

No Side Effects

There are no side effects - --no-immediate simply:

1. Skips the automatic npm install
2. Skips the automatic npm run dev

This gives you the "scaffolding only" behavior you saw.

Why It's Not Documented

Probably just an oversight in the help text. The negated form is technically the "default" behavior (when you don't pass --immediate), so documenting it may have seemed redundant.

You could open a small PR to add it to the help text for completeness if you'd like!