Show the current versions of the Juno CLI and emulator (if running). Use --version flag.

Run a custom JavaScript or TypeScript script in the CLI context. The script has access to the authenticated Juno environment.

Check the status of your modules (satellites, orbiters). Shows health, deployment status, and more.

Display the current authenticated profile, access key, and links to your satellite. Use this to verify authentication before running operations that require credentials.

Generate a juno.config file (TypeScript, JavaScript, or JSON). By default returns config content for preview. Set writeFile to true to write the file directly to disk. Then run juno_config_apply to push the config to your satellite.

Apply the current juno.config file to your satellite. This is required after modifying settings like storage headers, datastore rules, authentication config, or collection definitions.

Deploy your app's frontend files to your satellite. Reads from the source directory defined in juno.config and uploads all assets. Supports batch parallelism, clearing before deploy, and pruning stale files after.

Remove frontend files (JS, HTML, CSS, etc.) from your satellite. This does NOT remove user-uploaded files from custom collections — only the deployed app assets.

Remove stale frontend files from your satellite that are no longer in your build output. Use --dry-run to preview which files would be deleted without actually deleting them.

Build your serverless functions. Supports Rust, TypeScript, and JavaScript. The CLI auto-detects the language if not specified.

Generate the required files to begin developing serverless functions in your project. Scaffolds boilerplate for Rust, TypeScript, or JavaScript functions. Alias: juno functions init.

Publish a new version of your serverless functions to the satellite. Optionally submit as a pending change without applying, or provide a custom WASM file path.

Upgrade your satellite's serverless functions. Can use a local WASM file, select from CDN releases, or use the default local build output. Optionally create a snapshot before upgrading.

List all submitted or applied changes to your module. By default shows only submitted (pending) changes. Use --all for full history and --every to include all statuses.

Apply a submitted change by its ID. Optionally create a snapshot before applying and verify the change hash for integrity.

Reject a submitted change by its ID. This prevents the change from being applied. Optionally verify the change hash for integrity.

Scaffold a new Juno project. Uses Vite to create the frontend, then adds Juno SDK and config. Does NOT use the interactive create-juno CLI.

Fetch Juno documentation from GitHub repo. Full docs: https://github.com/junobuild/docs/tree/main/docs. Topics use underscore naming matching folder hierarchy (e.g. build_authentication, reference_cli_functions_build).