// docs / Ecosystem
Tools and editors
A CLI, a linter, a language server and two editor extensions. For a joke.
sh
vcwl new <dir> # starter app
vcwl dev # dev server with reload and in-page errors
vcwl build [--dev] # static site in dist/
vcwl serve # release build + server functions
vcwl check # type-check only
vcwl test # run test_* functions
vcwl fmt [--check] # format
vcwl lint # unused things, placeholder text, deep views
vcwl lsp # language server on stdin/stdout
vcwl upgrade # latest release, after a math quiz
vcwl deploy <netlify|pages|folder DIR> [--yes] # build, ceremony, manifest
vcwl doctor # environment and project checks
vcwl new --enterprise <dir> # a counter app in many layers
vcwl deploy builds, asks you to type the project name (unless --yes) and writes dist/.vcwl-manifest.json with the sha256 of every file. VCWL_DEPLOY_DRY_RUN=1 skips the upload. vcwl new --enterprise makes a working counter spread over domain, application and presentation layers, with factories and interfaces.
→
VS Code: editors/vscode, no dependencies. Package it with npx @vscode/vsce package.
→
Zed: editors/zed, with a tree-sitter grammar. "zed: install dev extension" and pick the folder.
→
The in-page debugger: element tree, computed styles, a picker and frame timings, in dev builds only.