@zaflun/lumio-cli 0.6.2 → 0.10.8

package/CHANGELOG.md

@@ -0,0 +1,190 @@
+# Changelog
+
+All notable changes to `@zaflun/lumio-cli` are documented here.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## 0.10.8
+
+### Added
+
+- **`CHANGELOG.md` ships in the package.**
+
+### Changed
+
+- **`lumio deploy --system` requires a changelog entry** — a system
+  extension deploy fails when `CHANGELOG.md` has no non-empty
+  `## [x.y.z]` section for the deployed version, in CI too, and `-d` does not
+  replace the entry. Third-party deploys keep their rule: a missing entry
+  stops the deploy only outside CI.
+- **`lumio dev` targets protocol 0.10.0** — the CLI warns when the project's
+  `@zaflun/lumio-sdk` or `@zaflun/lumio-devkit` speaks an older protocol, so
+  the Shopify event types (`shopify:order`, `shopify:order_paid`,
+  `shopify:product`) are not missing from the sandbox and `lumio trigger`.
+- **The sandbox preview follows the dashboard's URL rule** — images and links
+  in the extension UI load only from the sandbox page itself and the hosts in
+  `egress.allowHosts` of `lumio.config.json`. Anything else is dropped, as it
+  is on the dashboard.
+- **`lumio init` scaffolds React 19.3** — new projects get `react` and
+  `@types/react` `^19.3.0`, matching the SDK's renderer.
+- **Sandbox stylesheet rebuilt with Tailwind CSS 4.3.4.**
+- **Dependencies** — `inquirer` 14.2.5, `ora` 10 and `eventsource` 5.
+
+### Fixed
+
+- **`lumio deploy` from Windows** — bundle file paths are uploaded with `/`
+  separators instead of `\`, so the uploaded files are served under the
+  paths the extension references.
+- **`lumio logs` sends the token again** — the log stream authenticates with
+  the stored token through `eventsource` 5's `fetch` hook.
+
+## 0.10.0
+
+### Added
+
+- **A real `lumio dev`** — one session that builds the project with esbuild
+  in watch mode (the same pipeline as `lumio build`), serves a sandbox page on
+  `127.0.0.1:3100` and opens a REPL. The sandbox renders the editor and layer
+  surfaces and has panels for chat, events, channel point rewards, music,
+  scenarios, server functions, extension data and the log. Bot modules run
+  their chat, event, reward and timer handlers in the same session; the old
+  chat simulator is gone. New flags: `--platform`, `--role`, `--seed`,
+  `--no-cooldown`, `--view <target>` and `--open`; `--bot-module` now only
+  opens the chat first. Needs `@zaflun/lumio-devkit` in the project.
+- **`lumio trigger`** — sends an event, chat message, reward, music command,
+  timer, storage write or scenario to the running `lumio dev` from a second
+  terminal (`--field a.b=v`, `--tier`, `--data`, `--file`,
+  `--user` / `--role` / `--platform`, `--timer`, `--storage`). Load flags
+  `--count N`, `--rate 5/s` and `--random` send many at once.
+- **`dist/functions.json`** — `lumio build` writes a manifest of the named
+  functions in `server/functions.ts`, and bundles handler functions
+  (`query()` / `mutation()` / `action()`) into `dist/server.js`. Bot modules
+  can expose server functions too. `lumio deploy` refuses to upload when
+  `server/functions.ts` exists but the manifest was not built.
+- **Data schema upload** — `lumio deploy` sends `server/schema.ts` with the
+  version as its data schema (tables are provisioned on approval) and lists
+  schema errors the API rejects line by line.
+- **`lumio init` adds `@zaflun/lumio-devkit`** to new projects (except
+  automation nodes).
+
+### Changed
+
+- **The `interactive` target is gone** — `lumio.config.json` accepts only
+  `editor`, `layer` and `designer` and rejects any other target. Viewer input
+  comes through chat commands and channel point rewards handled by a bot
+  module. Breaking.
+- **`lumio env set`** stores a secret with `PUT …/secrets/{key}` and checks
+  the API's rules first: the key matches `^[A-Z0-9_]{1,64}$`, the value is
+  1 to 4096 bytes.
+- **Developer links** point to `/dashboard/settings/developer` (application)
+  and `/dashboard/settings/developer/limits` (limit increases).
+- **The `server/functions.ts` scaffold** orders `getItems` by `created_at`.
+
+## 0.6.2
+
+### Added
+
+- **Developer keys** — `lumio login --token` and `lumio deploy --token`
+  accept a developer key (`lm_dev_*`), the key to use for publishing. Without
+  `--token`, `lumio login` reads `LUMIO_TOKEN`.
+- **`lumio login` options** — `--id-url` and `--port` for the browser flow.
+- **Server bundle** — `lumio build` compiles `server/handler.ts` (or
+  `server/index.ts`) to `dist/server.js` for extensions with `"server": true`.
+- **Sound limit pre-flight** — `lumio deploy` checks the number, per-file size
+  and total size of declared sounds against your developer limits before it
+  uploads.
+- **`lumio env set <KEY> [VALUE]`** — without a value it reads `LUMIO_SECRET`
+  or prompts with hidden input, so the secret stays out of shell history.
+
+### Changed
+
+- **Browser login uses the ID app** — `lumio login` opens the Lumio login page
+  and exchanges the code at `/v1/auth/token/exchange`; it stores the session
+  and its refresh token. The callback server listens on `127.0.0.1` only and
+  exits as soon as the login finishes.
+- **Stricter config validation** — `extensionId` may contain only letters,
+  digits, `-` and `_` (max 64); bot-module platforms, automation `nodeType`
+  and `node.triggerMode` are checked against the shared lists.
+- **`lumio build` fails when Tailwind CSS fails** instead of shipping without
+  styles, and uses the project's own `@tailwindcss/cli` instead of `npx`.
+- **The source archive leaves out secrets** — `.env` files (except
+  `.env.example`), `.npmrc`, `.yarnrc` and `.lumio/`.
+- **Trovo is no longer a platform** — `lumio init` no longer offers it and the
+  config validator rejects it.
+- **`lumio --version`** prints the package version.
+- **Node.js 22.13 or newer is required.** Breaking.
+- **Dependencies** — `archiver` 8, `chalk` 6, `commander` 15, `esbuild` 0.28,
+  `eventsource` 4, `inquirer` 14, `open` 11.
+
+### Fixed
+
+- **`lumio deploy` error hints** — the HTTP status reaches the deploy command
+  again, so 409 / 413 / 401 failures print their guidance.
+- **`lumio run`** reports malformed JSON arguments instead of crashing.
+- **The credentials directory** is created readable by its owner only.
+
+## 0.5.2
+
+### Added
+
+- **Automation nodes** — `lumio init` scaffolds an `automation_node`
+  (action, trigger with webhook / polling, or logic), and `lumio dev` starts an
+  automation node simulator for it (`--automation-node`).
+- **`lumio init` wizard options** — editor approach (config schema, custom
+  `editor.tsx` or both), an optional visual designer for widgets and overlays,
+  and the styling (Tailwind CSS v4, plain CSS or inline). `lumio init` checks
+  for a developer profile first.
+- **CSS and assets in `lumio build`** — compiles `src/globals.css` (or
+  `style.css` / `index.css`) with Tailwind CSS v4 or copies it to
+  `dist/styles.css`, and emits imported images, media and fonts to
+  `dist/assets/`.
+- **`lumio deploy` options** — `--token` for CI and `--system` for system
+  extensions; `LUMIO_API_URL` overrides the API URL.
+- **Sound checks** — `lumio deploy` validates the sounds declared in
+  `lumio.config.json` (format, presence in `dist/sounds/`, size warning).
+
+### Changed
+
+- **`lumio deploy` uploads every file of `dist/`** individually (allowed
+  types only; max 200 files, 10 MB per file, 50 MB in total) instead of a
+  single bundle, and prints actionable hints for 409, 413 and 401 / 403.
+- **UI targets build as IIFE** with React and the SDK as runtime externals.
+- **The source archive** contains the whole project, minus `node_modules`,
+  `dist` and `.git`.
+
+## 0.3.0
+
+### Added
+
+- **Bot modules** — `lumio init` scaffolds a `bot_module` with platforms, a
+  `hello` command and `chat:read` / `chat:send`; `lumio dev` opens a chat
+  simulator for it (`--bot-module`); `lumio build` packs its `server/`.
+- **Bot handler types in `lumio run`** — `command`, `keyword`, `pattern`,
+  `event`, `timer` and `moderate`, with `--user`, `--role`, `--message` and
+  `--platform` for the mock chat user.
+- **`platforms` and `triggers`** in `lumio.config.json`; bot modules need at
+  least one platform.
+
+## 0.2.0
+
+### Added
+
+- **Browser login with PKCE** — `lumio login` without `--token` opens the
+  browser and waits for the callback on a local port.
+
+### Changed
+
+- **`lumio deploy`** writes the deployed version into the uploaded manifest.
+- **`lumio init`** points `$schema` at
+  `https://lumio.vision/schemas/lumio.config.schema.json`.
+
+## 0.1.0
+
+Initial release.
+
+### Added
+
+- **The `lumio` CLI** — `login`, `logout`, `whoami`, `init`, `dev`, `build`,
+  `deploy`, `status`, `logs`, `env`, `run` and `dashboard` for building,
+  testing and publishing Lumio extensions.

package/README.md

@@ -35,10 +35,11 @@ lumio deploy -v 1.0.0
 | `lumio logout` | Remove local credentials |
 | `lumio whoami` | Show current user and account |
 | `lumio init [name]` | Create a new extension project (interactive wizard) |
-| `lumio dev` | Start local dev server with hot-reload |
+| `lumio dev` | Run the extension locally: sandbox on `127.0.0.1:3100`, REPL and bot-module runtime in one session |
+| `lumio trigger <type\|@preset\|chat\|reward\|music\|scenario …>` | Send input to the running `lumio dev` from a second terminal (`--field a.b=v`, `--tier 2`, `--data`, `--file`, `--user/--role/--platform`, `--timer`, `--storage`; load: `--count N`, `--rate 5/s`, `--random`) |
 | `lumio build` | Bundle extension for deployment |
 | `lumio deploy` | Upload extension version (flags: `-v`, `-d`, `--breaking`, `--draft`) |
-| `lumio env set <KEY> <VALUE>` | Set a server-side secret |
+| `lumio env set <KEY> [VALUE]` | Set a secret (no `VALUE`: reads `LUMIO_SECRET` or prompts) |
 | `lumio env list` | List secret keys |
 | `lumio env delete <KEY>` | Delete a secret |
 | `lumio run <type:name>` | Execute a server function locally |