create
Scaffold a new vsceasy extension project into ./<name> (or --dir).
vsceasy create my-extensionFlags
| Flag | Type | Notes |
|---|---|---|
--name | text | Required. Package name, e.g. my-extension or @scope/my-ext. |
--displayName | text | Human-readable name. Defaults to a title-cased name. |
--description | text | Short description. |
--publisher | text | VS Code publisher id. Defaults to your-publisher. |
--ui | react | UI framework. Only react for now. |
--preset | minimal | full | full (default) adds a sample panel + RPC; minimal is empty. |
--dir | text | Target directory. Defaults to ./<name>. |
--git | boolean | Initialize a git repository. Skips the prompt; set --git=false to opt out. |
--install | boolean | Install dependencies (bun, falling back to npm). Skips the prompt; set --install=false to opt out. |
Examples
# interactive — prompts for the restvsceasy create my-extension
# fully scriptedvsceasy create \ --name my-extension \ --displayName "My Extension" \ --publisher my-publisher \ --ui react \ --preset full
# scoped name, custom directoryvsceasy create --name @acme/cool-tool --dir tools/coolAfter scaffolding
When run in an interactive terminal, create then offers to:
- Initialize a git repository (
git initin the project). - Install dependencies with the first available package manager (
bun, falling back tonpm).
Both default to yes. Pass --git / --install (or --git=false / --install=false) to skip the prompts — handy for scripting and CI:
vsceasy create --name my-extension --preset full --git --installIn non-interactive contexts (CI, piped input) without those flags the prompts are skipped and you run the steps yourself:
cd my-extensionbun installbun run dev # press F5 in VS CodeSee Quick start for the full first-run walkthrough.