Setup CLI

rabolic is the setup CLI. Run it in your project's folder:

npx rabolic init

It looks at the folder you run it in, then:

1. installs the right SDK with your package manager (npm, pnpm, yarn or bun; flutter pub add for Flutter);
2. adds one file that starts the SDK;
3. puts the key in your env file;
4. sends one test event (rabolic_cli_check), so you can watch it arrive on the Live page;
5. prints the one line you add yourself.

It only adds new files and appends to the env file. It never edits your existing code, and it never overwrites a file or an env value that is already there.

npm create rabolic does the same as npx rabolic init.

What it sets up

Sites and apps use the project's publishable key (rb_pub_…). A server uses a secret key (rb_live_… or rb_test_…). The CLI refuses the wrong kind. Both are in Integrations → API keys. See Keys.

The line you add yourself

The CLI doesn't edit your code, so it prints one step for you. For example:

• Next.js: render <Rabolic /> from the new file in your root layout, inside <body>.
• Nuxt: add runtimeConfig: { public: { rabolicKey: '' } } to nuxt.config. Nuxt fills it from NUXT_PUBLIC_RABOLIC_KEY.
• Vite: import the new file at the top of your entry file, such as src/main.ts.
• Node.js: import rabolic from the new file where you track server events or purchases.
• Expo Router: import the new file at the top of app/_layout.tsx, and pass the navigation ref to rabolic.trackNavigation for screens.
• Flutter: call Rabolic.init in lib/main.dart before runApp().
• Static site: paste the <script> tag into <head> on every page.

Options

npx rabolic init [--key <key>] [--host <url>] [--yes] [--dry-run] [--skip-install]
npx rabolic check --key <key> [--host <url>]

npx rabolic check --key … only sends the test event: a quick way to test a key, a host or a proxy.

What the test event tells you