Requirements
- macOS 12 or later, Linux x86_64 or arm64 (glibc), or Windows 10 or later.
- For package-manager installations, Node.js 22.3 or later, Deno 2.2 or later, or Bun 1.1 or later. The standalone binary includes its runtime.
- 2 GB of RAM for local development.
- Disk space for the selected CLI installation and project dependencies. See Install the CLI for current artifact sizes.
Blank or existing project
Add Veryfront Code to an existing or blank Node.js, Deno, or Bun project.react / react-dom,
which ship as dependencies of veryfront. It does not scaffold any files or
touch your package.json beyond the dependency entry. Add the four pieces
below yourself. veryfront init writes all of them for you, see
Create project.
Set the module type
Veryfront emits ES modules. Set"type": "module" in package.json:
package.json
npm init -y writes "type": "commonjs", and an existing project may have no
type field at all. Without "type": "module", veryfront build fails with
SyntaxError: Cannot use import statement outside a module.
Add the CLI scripts
package.json
Extend the base TypeScript config
Theveryfront package ships a base tsconfig.json with the compiler options
Veryfront expects, including "jsx": "react-jsx" and
"moduleResolution": "Bundler". Extend it:
tsconfig.json
Add a page and run it
Veryfront discovers routes underapp/. Create a home page:
app/page.tsx
http://localhost:3000 by default, to see the
page.
For where the remaining files go, see
Project structure. To add an API route under
app/api/, see Create API.
New scaffolded project
Create a new Veryfront Code project when you want scaffolding and starter files.Install the CLI
Install the CLI globally when you use Veryfront commands often.
These measurements describe recent releases and vary by platform and package
manager. A clean global npm installation used approximately 145 MB in one
measurement. Model weights are not included. The optional embedded ONNX runtime
adds approximately 500 MB, and supported model weights add 0.9 to 6 GB.
npm (recommended)
veryfront to your
shell path.
pnpm
yarn
bun
deno
npm:
specifier. Deno resolves that specifier from the current working directory, so
inside a project that depends on veryfront the global binary runs that
project’s version instead. Run veryfront --version outside any project
directory to see the globally installed version.
Standalone binary
Use the standalone binary when you need an executable that includes its own runtime. On macOS or Linux, run:SHA256SUMS
manifest; the binary is staged, checked against it, and only then moved into
place, so a mismatch installs nothing. Releases published before that manifest
existed have none, so pinning to one of those fails unless you set
VERYFRONT_INSTALL_SKIP_CHECKSUM=1 deliberately.
The commands still execute a script fetched at run time. To read it first, and
to pin a version instead of tracking latest:
SHA256SUMS published with the same release:
One-shot CLI usage
Usenpx when you do not want a global install:
veryfront CLI without installing it globally.
Use npm create veryfront when you want to scaffold a new project.
Coding-agent setup
Starter templates includeAGENTS.md. For older projects, install the shared
project guide with --target agents:
veryfront dev. It starts an HTTP MCP server two ports above the port
the dev server actually bound, always at the path /mcp. With the default port
3000 that is http://localhost:3002/mcp, so point your MCP-aware coding
agent there.
Read the port off the URL the dev server printed rather than off the --port
you asked for. When the requested port is taken, veryfront dev moves to the
next free one, and MCP follows it: a dev server that falls forward to 3001
serves MCP on 3003. The dev server lists the MCP address itself only under
--verbose. See Coding agents.
Verify the CLI
PATH entry takes effect.