Cli

The cli provides various commands to manage your project lifecycle, from creation to deployment.

Create Project

frizzante -cMyProject
# or
frizzante --create-project MyProject

Creates a new project in a new directory using the given name.

• DirectoryMyProject

  • main.go
  • …
  • Directoryapp

    • index.html
    • …

Generate

frizzante -g
# or
frizzante --generate

This command generates code and/or resources.

Note

Many of frizzante’s functionalities come as code and resource generations, not as packages.

Tip

Use :pick to run the interactive menu.

frizzante -g:pick

Configure

frizzante --configure

Runs —generate=“air,bun” and then —install.

This will generate Air and Bun binaries in .gen/{air,bun}.

• Directory.gen

  • Directoryair

    • air
  • Directorybun

    • bun

Install

frizzante -i
# or
frizzante --install

Installs Go and JavaScript packages from go.mod and app/package.json.

• go.mod
• Directoryapp

  • package.json

Note

JavaScript packages are installed using .gen/bun/bin by default. You can point to a custom Bun binary of your choice by setting --bun.

For example, the following will install JavaScript packages using a ~/.bun/bun binary

frizzante --bun="~/.bun/bun" --install

Alternatively you can also use a global binary.

frizzante --bun="bun" --install

This will force the cli to use the binary present in your path.

Update

frizzante -u
# or
frizzante --update

Updates Go and JavaScript packages from go.mod and app/package.json.

• go.mod
• Directoryapp

  • package.json

Caution

This will bump version numbers.

Note

JavaScript packages are updated using .gen/bun/bin by default. You can point to a custom Bun binary of your choice by setting --bun.

For example, the following will update JavaScript packages using a ~/.bun/bun binary

frizzante --bun="~/.bun/bun" --update

Alternatively you can also use a global binary.

frizzante --bun="bun" --update

This will force the cli to use the binary present in your path.

Package

frizzante -p
# or
frizzante --package

Runs vite build and vite build --ssr in order to package the the app directory into app/dist.

• Directoryapp

  • Directorydist

    • Directoryclient

      • Directoryassets

        • index-{hash}.css
        • index-{hash}.js
        • …
      • index.html
    • server.js

The output contains a client directory which can be simply served as is to the client and a server.js file that can be executed on the server in order to render the contents of the application in advanced.

Note

Your app directory is packaged using .gen/bun/bin by default. You can point to a custom Bun binary of your choice by setting --bun.

For example, the following will package your app using a ~/.bun/bun binary

frizzante --bun="~/.bun/bun" --package

Alternatively you can also use a global binary.

frizzante --bun="bun" --package

This will force the cli to use the binary present in your path.

Package Watch

frizzante --package-watch

Runs —package in watch mode.

Note

This will detect changes made only in the app directory.

Dev

frizzante -d
# or
frizzante --dev

Runs Air and —package-watch in parallel.

Note

The cli uses .gen/air/air by default. You can point to a custom Air binary of your choice by setting --air.

For example, the following will run air using a ~/.air/air binary

frizzante --air="~/.air/air" --dev

You can also use a global binary.

frizzante --air="air" --dev

Or even use custom paths for both Air and Bun.

frizzante --air="air" --bun="bun" --dev

This will force the cli to use the binaries present in your path.

Build

frizzante -b
# or
frizzante --build

Runs —package and then builds the Go program in .gen/bin/app.

• Directory.gen

  • Directorybin

    • app

Check

frizzante --check

Runs eslint and svelte-check in your app directory in order to detect code syntax and style errors.

Note

Checks are run using .gen/bun/bin by default. You can point to a custom Bun binary of your choice by setting --bun.

For example, the following will check your app using a ~/.bun/bun binary

frizzante --bun="~/.bun/bun" --check

Alternatively you can also use a global binary.

frizzante --bun="bun" --check

This will force the cli to use the binary present in your path.

Format

frizzante -f
# or
frizzante --format

This will run go fmt ./... and prettier --write . in your app directory.

Note

Prettier is run using .gen/bun/bin by default. You can point to a custom Bun binary of your choice by setting --bun.

For example, the following will format your app using a ~/.bun/bun binary

frizzante --bun="~/.bun/bun" --format

Alternatively you can also use a global binary.

frizzante --bun="bun" --format

This will force the cli to use the binary present in your path.

Touch

frizzante --touch

Creates placeholder files in app/dist.

Note

This is just a pure convenience command.

Go’s embed directive requires files to exist at compile time, this command simply creates some placeholders in your app/dist directory.

Clean Project

frizzante --clean-project

Removes directories .gen, .vite, app/dist, app/node_modules and then runs —touch.

Note

These are all files that can easily be recreated with --configure followed by --package.

Reset

frizzante --reset

Deletes frizzante’s global cache.

Note

The global cache is located at ~/.frizzante by default.

Tip

You can configure this location by setting FRIZZANTE_HOME to whatever path you want in your environment variables.

Additional Options

Confirmation

frizzante -y
# or
frizzante --yes

Automatically confirms all prompts without user interaction.

Tip

This is useful for ci/cd pipelines, automated scripts, batch operations.

Version

frizzante -v
# or
frizzante --version

Displays the version of the binary.

Help

frizzante -h
# or
frizzante --help

Shows the complete list of available commands and options.

Interactive Mode

frizzante

Running frizzante without any flags starts an interactive menu where you can select commands using arrow keys.

Note

This is useful if

• you’re learning the available commands
• you’re not sure which command to use
• you prefer a guided interface