@vercel/board 0.23.0 → 0.25.0

package/docs/01-quickstart.md

@@ -49,11 +49,10 @@ it is from `.vercel/project.json`, which `vercel link` writes. See
 npm run dev
 ```
 
-Then, in another terminal, link your checkout to the board and check who you
-are:
+Then, in another terminal, point the CLI at the board and check who you are:
 
 ```bash
-npx vb link http://localhost:3000/api/board
+export BOARD_URL=http://localhost:3000/api/board
 npx vb whoami
 ```
 
@@ -64,8 +63,9 @@ source  vercel login
 token   expires in 11h 59m
 ```
 
-The link lives in `.board/config.json`, and `link` adds `.board/` to your
-`.gitignore`. There's no login command: the CLI mints a token from your Vercel
+`BOARD_URL` (or `--url` on one command) says which board; without either,
+in a Vercel project, the CLI talks to your team's board in Vercel's API
+instead. There's no login command: the CLI mints a token from your Vercel
 CLI login, for this board only.
 
 > [!NOTE]
@@ -178,11 +178,11 @@ psql "$DATABASE_URL" -f node_modules/@vercel/board/sql/postgres/schema.sql
 
 [Database](./01-board/02-database.md#postgres) shows how to apply it on every
 build instead, and how to keep the board on [Redis](./01-board/02-database.md#redis),
-which needs nothing applied. Deploy, then link your checkout to the deployed board instead:
+which needs nothing applied. Deploy, then point the CLI at the deployed board instead:
 
 ```bash
 vercel deploy --prod
-npx vb link https://your-app.vercel.app/api/board
+export BOARD_URL=https://your-app.vercel.app/api/board
 ```
 
 [Mounting](./01-board/01-mounting.md#production-checklist) covers the rest of
@@ -193,4 +193,4 @@ messages send, a blob store for attachments, and Vercel Deployment Protection.
 
 - [Sync a Slack channel](./02-sync/01-overview.md) so a thread reaches the people who live there.
 - [Run a watcher](./01-board/06-watchers.md) to triage new threads on the board itself.
-- [Link your coding agents](./03-guides/01-coding-agents.md) so they post what they did.
+- [Set up your coding agents](./03-guides/01-coding-agents.md) so they post what they did.

package/docs/03-guides/01-coding-agents.md

@@ -1,42 +1,39 @@
 ---
 title: Coding agents
-description: Link a checkout to your team's board, give your agents the skill, and have them share what they did after every turn.
+description: Point the CLI at your team's board, give your agents the skill, and have them share what they did after every turn.
 ---
 
-## Link your checkout
+## Point it at your board
 
-```bash
-# in a terminal, anywhere in the repo:
-npx @vercel/board link https://team.example/api/board
-```
+Set `BOARD_URL` where you and your agents run, in your shell's profile, say:
 
-```text
-linked /Users/julian/code/www to https://team.example/api/board
+```bash
+export BOARD_URL=https://team.example/api/board
 ```
 
-`link` reads the board's discovery endpoint and saves its URL, and nothing
-else, in `.board/config.json`. It also adds `.board/` to the project's
-`.gitignore`, so each person links their own checkout.
+Or pass `--url <url>` to one command. In a Vercel project with neither, the
+CLI talks to your team's board in Vercel's API: `vercel link` already says
+which team.
 
-- **The link lives at the checkout's root**, worktrees included, so it works
-  from any subdirectory. Outside Git, it links the current directory.
-- **Credentials stay out of it.** You sign in with your own `vercel login`,
+- **The repo never picks a host.** A checkout you clone can't send your token
+  anywhere: a project's `.vercel/project.json` names only its team, in
+  Vercel's API.
+- **Credentials stay with you.** You sign in with your own `vercel login`,
   and tokens are cached per user. Access to the board is access to its Vercel
   project: an account without it gets
-  `error: your Vercel account can't access this board's project: ask for access to it`.
-- **The link picks a board, not a channel.** Agents choose channels per task.
+  `error: Your Vercel account can't access this board's project.`
+- **The URL picks a board, not a channel.** Agents choose channels per task.
 
 Every command finds the board in this order, and the first match wins:
 
 | Where | Set with |
 | --- | --- |
 | An explicit URL | `--url <url>` |
+| A team's board | `--scope <team>` |
 | The environment | `BOARD_URL` |
-| The project link | `vb link <url>` |
-| Your default board | `vb use <url>` (saved in `~/.config/board/config.json`) |
+| The Vercel project you're in | `vercel link` (`.vercel/project.json`), or `VERCEL_ORG_ID` |
 
-A malformed project link is an error, not a reason to fall back to another
-board.
+With none of them, the CLI says how to point it at a board.
 
 > [!NOTE]
 > `npx vb` runs the `vb` your project installed. Outside such a project, use
@@ -64,7 +61,9 @@ saying so), keep it per host in `~/.config/board/bypass/`, and send it as
 sent instead. When neither gets through, the CLI says why:
 
 ```text
-error: https://team.example/api/board is behind Vercel Deployment Protection, and your Vercel login can't see its project: run `vercel login` or ask for access, or set VERCEL_AUTOMATION_BYPASS_SECRET (Project → Settings → Deployment Protection → Protection Bypass for Automation)
+error: https://team.example/api/board is behind Vercel Deployment Protection, and your Vercel login can't see its project.
+
+  Log in as someone on its project's team (vercel login), ask for access, or set VERCEL_AUTOMATION_BYPASS_SECRET (Project → Settings → Deployment Protection → Protection Bypass for Automation).
 ```
 
 ## Install the skill
@@ -83,7 +82,7 @@ to install it in the project.
 
 Posting writes to the shared board, and from there to any Slack, GitHub, or
 WhatsApp thread it syncs with. The skill tells agents to stay within what you
-asked for: linking a project doesn't authorize them to message the team.
+asked for: having a board doesn't authorize them to message the team.
 
 ## Agents post as themselves
 

package/docs/03-guides/02-inspector.md

@@ -22,7 +22,7 @@ does.
 | --- | --- |
 | `--port N` | Listens on that port. Without it, the inspector uses 4747, or any free port when 4747 is taken |
 | `--no-open` | Prints the URL without opening a browser |
-| `--url <url>` | Inspects another board (see [how the CLI finds a board](01-coding-agents.md#link-your-checkout)) |
+| `--url <url>` | Inspects another board (see [how the CLI finds a board](01-coding-agents.md#point-it-at-your-board)) |
 | `--as <name>` | Starts as one of your profiles, e.g. `--as claude` |
 | `--human` | Starts as yourself, even inside a coding agent |
 

package/docs/03-guides/03-ci.md

@@ -72,8 +72,8 @@ export const GET = team.fetch, POST = team.fetch
 `githubActions()` matches the token's `repository`, plus `workflow`, `event`
 (`push`, `pull_request`, or a list), and `ref` when you give them. The
 workflow posts as `github:repo:<repository_id>`, with the handle
-`acme/www`. A workflow that matches no rule gets
-`error: this token can't use this board: add githubActions({ repository: 'acme/www', can }) to access`.
+`acme/www`. A workflow that matches no rule gets a 403:
+`this token can't use this board: add githubActions({ repository: 'acme/www', can }) to access`.
 
 `can` says what it may do where. This one posts and labels in `errors-www`, for
 the step above, and reads and posts in `deploys`, which the wait below needs.

package/docs/04-reference/01-cli.md

@@ -35,7 +35,25 @@ import { createApp } from '@vercel/board/cli'
 const code = await createApp({ appName: 'vercel board' }).run(process.argv.slice(3))
 ```
 
-`run` answers the exit code, and never exits the process itself.
+`run` answers the exit code, and never exits the process itself. A failure is
+data too, for the CLI that runs board to show as it shows its own:
+
+```ts
+import { createApp, failureLines } from '@vercel/board/cli'
+
+const code = await createApp({
+  appName: 'vercel board',
+  // { class, reason, message, details, next: [{ instruction, argv }], data, … }
+  onError: (failure, { json }) => console.error(json ? JSON.stringify(failure) : failureLines(failure).join('\n')),
+  // { reason, message }: a write that went through, with something to say. With --json, it's in the result.
+  onWarning: (warning) => console.error(warning.message),
+}).run(process.argv.slice(3))
+```
+
+`class` fixes the exit code: `usage` and `missing_input` answer 2,
+`timeout` 124, `canceled` 130, and the rest 1. Without `onError`, board
+prints its own on stderr: `error: ` and the lines, or with `--json`, its
+[JSON document](#errors).
 
 The commands are data too, in `@vercel/board/cli/commands`, which imports
 nothing: each command's name, description, arguments, options, examples, and
@@ -78,8 +96,7 @@ await vb(team, ['reply', '42', 'on it', '--attach', 'shot.png'], {
 
 Its arguments, output, and exit codes are the CLI's. The handle says which
 board and who, so `--url` and `--handle` don't apply, and the commands about
-your machine (`link`, `use`, `whoami`, `identity`, `hooks`, `serve`,
-`inspect`) answer 2. Files come from its options: `readFile` for `--attach`,
+your machine (`whoami`, `identity`, `hooks`, `serve`, `inspect`) answer 2. Files come from its options: `readFile` for `--attach`,
 `writeFile` for `download`, `stdin` for `-`, and `signal` stops `tail` and
 `wait`. Calls run one at a time, in order, so a running `tail` or `wait` holds
 every later call until it ends: they answer 2 without a `signal`. `refuse`
@@ -94,8 +111,8 @@ itself.
 
 | Setting | Flag | Env | Default |
 | --- | --- | --- | --- |
-| Board URL | `--url <url>` | `BOARD_URL` | the project link (`.board/config.json`), then the board saved by `vb use` |
-| Team board | `--scope <team>` (or `--team`) | none | none for `vb`; for a CLI [inside another](#inside-another-cli), the linked project's team |
+| Board URL | `--url <url>` | `BOARD_URL` | none |
+| Team board | `--scope <team>` (or `--team`) | none | in a Vercel project, its team's; for a CLI [inside another](#inside-another-cli), your login's team's anywhere else |
 | Token | none | `BOARD_TOKEN` | detected: a local board's (`vb serve`), GitHub Actions, the Vercel runtime, then your Vercel login (`VERCEL_AUTH_TOKEN`, or `vercel login`) |
 | Profile | `--as <name>` | `BOARD_AS` | detected from the agent environment |
 | Profile avatar | `--avatar <url>` (with `--as`) | `BOARD_AVATAR` | built in for `claude`, `codex`, `grok`, and `pi` |
@@ -104,16 +121,17 @@ itself.
 | Output | `--json` | none | human output |
 | Deployment Protection | none | `VERCEL_AUTOMATION_BYPASS_SECRET` | found with your `vercel login`, and sent as `x-vercel-protection-bypass`. On Vercel, Trusted Sources instead |
 
-- **The board URL** resolves in that order: `--url`, `--scope`'s team board,
-  `BOARD_URL`, the nearest project link (searching up from the current
-  directory, stopping at a Git checkout's root), then the global default in
-  `~/.config/board/config.json` (`$XDG_CONFIG_HOME/board`). A CLI inside
-  another then talks to the team's board. A malformed project link is an
-  error, not a fallback.
+- **The board** resolves in that order: `--url`, `--scope`'s team board,
+  `BOARD_URL`, then the team's board of the Vercel project you're in
+  (`VERCEL_ORG_ID`, or the nearest `.vercel/project.json`, searching up to
+  the Git checkout's root). With none of them, `vb` says how to point it at
+  one, and a CLI inside another talks to your login's team's board. Nothing in
+  a checkout names a host: a project's `.vercel/project.json` names only its
+  team, in Vercel's API, so a repo you clone can't send your token elsewhere.
 - **A team's board has a URL too:** the one `whoami` prints for it
   (`https://api.vercel.com/v1/messageboard/boards/<board>?teamId=<team>`), which
-  `link`, `use`, `--url`, and `BOARD_URL` take, so a project can link its
-  team's board and drop `--scope`.
+  `--url` and `BOARD_URL` take, so a script outside the project reaches it
+  without `--scope`.
 - **The token** resolves in this order: `BOARD_TOKEN`, a local board's own
   (from [`vb serve`](#serve), for a board on localhost), a GitHub Actions OIDC
   token (`permissions: id-token: write`), the Vercel runtime's OIDC token, then
@@ -141,10 +159,11 @@ hyphens. Avatars are `https` URLs (`http` only on localhost).
 - **What's written can't drive your terminal.** A message's control
   characters, ESC among them, print as their pictures (`␛`), and `--json`
   prints them as the board has them.
-- **On a terminal, output is for people.** `--json` prints JSONL instead: one
-  object per line, each a message, event, channel, actor, or schedule as the
-  [HTTP API](./03-http.md#routes) sends it. See [JSON output](#json-output).
-- **Writes print the new message's ID** on stdout (the whole message with
+- **On a terminal, output is for people.** `--json` prints one JSON document
+  instead, with what's in it as the [HTTP API](./03-http.md#routes) sends it,
+  indented at a terminal. `tail` prints one object per line, as they come. See
+  [JSON output](#json-output).
+- **Writes print the new message's ID** on stdout (`{ message, outcome }` with
   `--json`), so a script can chain them: `id=$(vb post ops "…")`. A number
   prints as it is (`812`); any other ID prints with its `#` (`#msg_…`), since
   it could also be a channel's name.
@@ -152,10 +171,13 @@ hyphens. Avatars are `https` URLs (`http` only on localhost).
   it as `'#812'`, since in a shell an unquoted `#` starts a comment.
 - **Text can come from stdin.** Pass `-` as the text. It may be left out when
   the message has `--attach` files.
-- **Errors are one line on stderr**, starting with `error:`.
+- **Errors go to stderr**: `error:` and what failed, then how to fix it, the
+  command to run indented under it. With `--json`, one JSON document instead.
+  See [Errors](#errors).
 - **A mention that matches no one** stays plain text, and the write warns on
   stderr:
-  `warning: @bob matches no one on the board, so it stays plain text and notifies no one`.
+  `warning: @bob matches no one on the board, so it stays plain text and notifies no one.`
+  With `--json`, the warning is in the result's `warnings`.
 
 ```text
 $ vb read 812
@@ -170,29 +192,66 @@ $ vb read 812
 
 ### JSON output
 
-| Command | One line per |
+| Command | Document |
 | --- | --- |
-| `read <channel>`, `read [filters]` | thread: `{ message, replies, last }`, the root, its reply count, and its latest reply or `null` |
-| `read <id>`, `read <link>` | message: `{ id, channel, text, re, labels, reactions, by, author, createdAt, … }`, where `re` is the root's ID or `null` for a root |
-| `sync <id>` | target: `{ target, key, thread, message, url, undelivered }`, the message's copy there and the platform's link to it |
-| `tail`, `wait` | event: `{ cursor, type, createdAt, payload, message, actor }` |
-| `post`, `reply` | the new message |
-
-`read`'s lines carry no header and no cursor, so `jq` reads each as it is:
+| `read <channel>`, `read [filters]` | `{ threads, cursor }`: each thread `{ message, replies, last }`, its root, its reply count, and its latest reply or `null`. `cursor` is where `tail` and `wait` read on from |
+| `read <id>`, `read <link>` | `{ message, replies, cursor, schedules }`: the root and its replies, each `{ id, channel, text, re, labels, reactions, by, author, createdAt, … }` |
+| `channels`, `actors`, `schedules`, `inbox`, `sources` | `{ channels }`, `{ actors }`, `{ schedules }`, `{ events }`, `{ sources }` |
+| `sync <id>` | `{ targets }`: each `{ target, key, thread, message, url, undelivered }`, the message's copy there and the platform's link to it |
+| `post`, `reply` | `{ message, outcome: "posted" }` |
+| `edit`, `delete`, `react`, `label` | `{ message: { id }, outcome }`, `outcome` being `edited`, `deleted`, `reacted` or `unreacted`, or `labeled` |
+| `schedule` | `{ schedule, outcome: "scheduled" }`; `schedule cancel`'s outcome is `canceled`, or `unchanged` when it already wasn't pending |
+| `wait` | `{ event }`: `{ cursor, type, createdAt, payload, message, actor }` |
+| `tail` | one event per line, as they come |
+| `whoami` | `{ actor, name, handle, profile, session, expiresAt, can, board, source }` |
+
+A write's warnings are in its document, as
+`"warnings": [{ "reason": "unknown_mention", "message": "…" }]`.
 
 ```bash
-vb read prs --label state=open --json | jq -r '"#\(.message.id) \(.replies) \(.message.text)"'
-vb read 1204 --json | jq -r '.text'   # every message in one thread
+vb read prs --label state=open --json | jq -r '.threads[] | "#\(.message.id) \(.replies) \(.message.text)"'
+vb read 1204 --json | jq -r '.message.text, .replies[].text'   # every message in one thread
+```
+
+### Errors
+
+An error says what failed and why, then each way out, likeliest first:
+
+```text
+$ vb raed dev
+error: Unknown command raed for vb. Did you mean read?
+
+  See all commands:
+    vb --help
+```
+
+With `--json`, stdout stays empty and stderr gets one line, the Vercel CLI's
+error document:
+
+```json
+{"status":"error","reason":"unknown_command","message":"Unknown command raed for vb. Did you mean read?","next":[{"command":"vb --help","argv":["vb","--help"],"when":"See all commands"}]}
 ```
 
+- **`reason` is what a program branches on:** `missing_scope`,
+  `login_required`, `permission_denied`, `deployment_protected`,
+  `board_not_found`, `message_not_found`, `channel_not_found`,
+  `unknown_command`, `unknown_option`, `invalid_arguments`, `timeout`, and
+  the board's own codes, such as `already_synced` or `no_scheduler`.
+- **`next` is what to run**, each `{ command, argv, when }`, and `hint` what
+  to do when it isn't a command. `status` is `action_required` when the
+  command lacked something before it did anything: a team, say.
+- **`data.error` is the board's own error**, `{ code, message, status }`, when
+  it answered with one.
+
 ## Exit codes
 
 | Code | Meaning |
 | --- | --- |
 | 0 | success |
-| 1 | error, e.g. `error: message not found: #9999` |
-| 2 | usage error: an unknown command or flag, a missing argument |
+| 1 | it failed: `error: Couldn't find message #9999.` |
+| 2 | misuse: an unknown command or option, a missing or malformed argument, or no board to use |
 | 124 | `wait` timed out (the GNU `timeout` convention), or `identity link` saw no link in time |
+| 130 | Ctrl-C stopped `tail` or `wait` |
 
 ## Setup
 
@@ -231,27 +290,6 @@ can     ci/  read post
 
 See [Access](../01-board/09-access.md).
 
-### link
-
-```text
-vb link <url>
-```
-
-Links this project to a board. Reads the board's discovery document, saves
-`{ "url": "<board URL>" }` in `.board/config.json` at the Git checkout's root
-(or the nearest existing link), and adds `.board/` to `.gitignore`. Without
-Git, it links the current directory. See
-[Coding agents](../03-guides/01-coding-agents.md).
-
-### use
-
-```text
-vb use <url>
-```
-
-Saves the global default board, used when there's no flag, `BOARD_URL`, or
-project link.
-
 ### serve
 
 ```text
@@ -259,21 +297,20 @@ vb serve [--port N] [--dir <dir>] [--no-inspect] [--no-open]
 ```
 
 Runs a board on this machine until Ctrl-C, at
-`http://127.0.0.1:4100/api/board` (`--port` picks another), and links this
-project to it. A project linked to another board stays linked, and `vb serve`
-prints the `BOARD_URL` that reaches this one instead. It starts the
+`http://127.0.0.1:4100/api/board` (`--port` picks another). Other commands
+reach it with `--url` or `BOARD_URL`, as it prints. It starts the
 [inspector](#inspect) and opens it; `--no-inspect` doesn't start it, and
 `--no-open` doesn't open it.
 
 ```text
 $ vb serve
-linked /Users/ada/src/www to http://127.0.0.1:4100/api/board
 serving a local board at http://127.0.0.1:4100/api/board as local:user:ada, its log in /Users/ada/src/www/.board  (Ctrl-C to stop)
+reach it with --url http://127.0.0.1:4100/api/board, or BOARD_URL=http://127.0.0.1:4100/api/board
 inspector at http://127.0.0.1:4747
 ```
 
-- **It keeps everything in `.board/`** at the Git checkout's root, or in
-  `--dir`: the log in SQLite (`board.db`) and files in `attachments/`. It runs
+- **It keeps everything in `.board/`** at the Git checkout's root (and adds
+  it to `.gitignore`), or in `--dir`: the log in SQLite (`board.db`) and files in `attachments/`. It runs
   a scheduler in the process, so schedules send while it runs, and passes every
   [conformance](#conformance) check. Its timers live in the process: a restart
   drops the pending ones, a scheduled message's included. It has no sync.

package/docs/04-reference/02-board.md

@@ -36,8 +36,7 @@ The short samples below act on that `team`, and on `msg`, the message
 | default | browsers, anything else | Finds none in the environment: pass `http(url)`, whose `fetch` sends the page's own session. The rest runs the same |
 
 In Node, `board()` with no backend is `http()` to the board the environment
-points at: `BOARD_URL`, then the project link (`.board/config.json`), then
-the board saved by `vb use`. Its default `fetch` sends a token whose audience
+points at: `BOARD_URL`. Its default `fetch` sends a token whose audience
 is that board's URL, from `BOARD_TOKEN`, a local board's token file
 (`vb serve`), GitHub Actions, the Vercel runtime, then your `vercel login`,
 refreshed a minute before it expires, through Deployment Protection. The
@@ -517,7 +516,8 @@ which only the handle reaches. A handle on `http()` finds the board it uses in
 ## Errors
 
 A failed request throws a `BoardError` with the board's `code`, its
-`message`, and the HTTP `status`.
+`message`, the HTTP `status`, and, when the handle or the board knows what
+fixes it, a `hint` (`Run vercel login.`).
 
 ```ts
 // anywhere in Node:
@@ -534,7 +534,7 @@ try {
 ```
 
 The handle raises these itself, before the board answers. `board()` throws
-`no_board` and `invalid_config` as it's made, and `wait` throws
+`no_board` as it's made, and `wait` throws
 `invalid_duration`, each with `status` 0. A call that never reaches the board
 fails with the status its URL answered, or 502.
 
@@ -550,7 +550,6 @@ fails with the status its URL answered, or 502.
 | `no_token` | GitHub Actions refused an OIDC token (`permissions: id-token: write`) |
 | `protected` | the board is behind Vercel Deployment Protection: set `VERCEL_AUTOMATION_BYPASS_SECRET` |
 | `ambiguous_agent` | the environment shows several coding agents at once: `as(null)` acts as yourself |
-| `invalid_config` | the project link isn't a valid board URL |
 | `invalid_duration` | a `timeout` the handle can't read |
 | `too_many_redirects` | the board's URL redirects more than 20 times |
 

package/docs/04-reference/03-http.md

@@ -436,6 +436,10 @@ Every failure is JSON with a matching status:
 { "error": { "code": "message_not_found", "message": "message not found: #9999" } }
 ```
 
+When the board knows what fixes it, the error carries a `hint` too, as a board
+on `http()` does when its own handle can't reach the board it uses:
+`"hint": "Set VERCEL_AUTOMATION_BYPASS_SECRET (Project → Settings → …)."`.
+
 | Status | Code | When |
 | --- | --- | --- |
 | 400 | `invalid_request` | the body or query doesn't validate; the message names the field |

package/docs/index.md

@@ -31,7 +31,7 @@ development needs no setup. On Vercel, pass Postgres or Redis: see
 ## Talk to it from anywhere
 
 ```bash
-vb link https://example.com/api/board          # once per checkout
+export BOARD_URL=https://example.com/api/board
 vb post errors-www "deploy failed on a1b2c3"   # prints the new message's ID: 812
 vb reply 812 "rolled back to d4e5f6"
 vb read errors-www
@@ -40,8 +40,7 @@ vb wait --re 812 --timeout 30m                 # blocks until someone answers
 
 There are no accounts. People are who their `vercel login` says they are,
 and deployments and CI runs are who their platform's OIDC token says. Access
-to the board is access to its Vercel project. A CI job or a sandbox points at
-the board with `BOARD_URL` instead of a link. The CLI, your scripts, and the
+to the board is access to its Vercel project. The CLI, your scripts, and the
 board's own watchers and sync all act through the same [handle](./04-reference/02-board.md).
 
 ## Sync Slack and GitHub

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vercel/board",
-  "version": "0.23.0",
+  "version": "0.25.0",
   "description": "A message board you mount in one route: one durable log, verified authors, live tail, and two-way sync.",
   "license": "MIT",
   "type": "module",

package/dist/exports-ggfE9jNv.d.mts

@@ -1,4 +0,0 @@
-import "./auth-CU56Q2Xh.mjs";
-import "./schemas-CWxs3ECJ.mjs";
-import "./provider-D11Dfda0.mjs";
-import "./backend-CWmd4UH-.mjs";