@bardioc/create-bardioc-app

Scaffold a Vite app wired for @bardioc/app-sdk.

Requirements

• Node.js >=20.19.0

Install

Install the CLI globally from the public npm registry:

npm install -g @bardioc/create-bardioc-app

If your default npm registry is not https://registry.npmjs.org/, set it in your user-level npm config before installing app dependencies.

You can also run it without a global install:

npm exec --yes @bardioc/create-bardioc-app my-app -- --port 3005

Quick start

create-bardioc-app my-app --port 3005
cd my-app
npm install

Copy .env.example to .env and fill in VITE_APP_NAME, DEV_SECRET, and API_BASE_URL. Then run npm run dev.

Generated app

The generated app includes:

• React + Vite project structure (or your chosen --template)
• @bardioc/app-sdk dependency
• AppSdkProvider wiring
• optional standalone dev-auth wiring via .env (DEV_SECRET proxy)
• a compact SDK demo with notification and transport examples
• public/app-manifest.json

Release infra (out of the box)

Every scaffolded app ships a lightweight versioning toolkit:

• Changesets (.changeset/ + changeset/release:* scripts) for semver-versioning the app
• scripts/stamp-manifest.mjs — folds package.json's version into the built app-manifest.json so the WebOS app store shows the real release version (wired into npm run build / npm run bundle)
• Two Claude skills under .claude/commands/: /changeset-app (bump locally) and /refresh-bundle (rebuild the zip and swap it into a WebOS host checkout)

Opt-in tooling

Heavier, environment-specific tooling is off by default — pass a flag to include it:

• --with-pipeline — a Bitbucket pipeline (bitbucket-pipelines.yml) running check-types/build/audit on PRs, with a publish step on dev. Publishing is dormant while the app stays "private": true + unscoped (pnpm changeset publish no-ops); the generated README.md documents how to enable it.
• --with-link — the link:source / unlink:source dev flow (scripts/link-source.mjs + pnpm-workspace.yaml + .npmrc) for developing against an in-tree @bardioc/* source checkout.

Standalone dev auth

Generated apps can run standalone with the DEV_SECRET dev-auth proxy.

1. Copy .env.example to .env
2. Fill in VITE_APP_NAME, DEV_SECRET, and API_BASE_URL
3. Run npm run dev

When running outside the host iframe, the SDK proxies /rest/* to API_BASE_URL with the X-Dev-Secret header and installDevBridge() handles SDK messages. Vite templates do this through the bardiocDevAuth plugin; the angular and nextjs templates run scripts/dev-auth-proxy.mjs, which npm run dev starts alongside their dev server.

Options

• --template <name> — framework template (default vite)
• --port <port> — dev server port, default 3005
• --with-pipeline — add the Bitbucket CI/publish pipeline (off by default)
• --with-link — add the link:source dev flow for local @bardioc/* checkouts (off by default)

Support

For support, contact [email protected].

License

MIT.

Copyright (c) 2026 ALMATO AG. All rights reserved.

This is an internal library for ALMATO AG.