Skip to main content

Daily Development: Running Scripts & Local Debugging

In rabetbase, the command related to "running commands in this frontend project" is primarily run. It doesn't try to guess what you want to do -- it reads the scripts from the current directory's package.json and executes them using the detected package manager (bun / pnpm / yarn / npm).

List available scripts in the current project​

rabetbase run

Without arguments, this lists all script names from package.json, so you can quickly confirm whether start, build, preview, etc. are available.

Run a script​

rabetbase run start
rabetbase run build
rabetbase run test

The script name must match what's defined in your project.

Special handling for start / dev​

When running start or dev, the CLI performs a version check (for both the CLI itself and the project's SDK). If a newer version is available, it will show a prompt. This helps reduce issues caused by "old scaffolding + new platform behavior." A prompt doesn't mean failure, but if your team requires version consistency, it's a good idea to upgrade as suggested.

Preview and watch​

rabetbase run preview

If your template supports it, you can add:

rabetbase run preview --watch

This starts build watching and preview in parallel based on the CLI's built-in logic (actual behavior depends on the preview script in your project's package.json).

Migration from old command habits​

You may be used to running:

rabetbase start
rabetbase build

In v2, these are deprecated and will prompt you to use instead:

rabetbase run start
rabetbase run build

One rule to remember: always add run when executing npm scripts, and they won't conflict with rabetbase's own subcommands (like dataset, sql, etc.).

Summary​

  • rabetbase run = the package.json script runner for the current project.
  • start / dev include version checks.
  • The legacy rabetbase start should be replaced with rabetbase run start.

Next: To pull API definitions from the platform and explore data, read API & Datasets.