@fui-org/fui-cli 1.1.0 → 1.2.1

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fui-org/fui-cli",
-  "version": "1.1.0",
-  "description": "Token-lean CLI for the FUI low-code platform (Bun or Node.js), successor to Fui MCP",
+  "version": "1.2.1",
+  "description": "Token-lean CLI for the FUI low-code platform (Node.js), successor to Fui MCP",
   "keywords": [
     "ai",
     "bun",
@@ -23,9 +23,8 @@
     "access": "public"
   },
   "scripts": {
-    "fui": "bun src/bin.ts",
-    "build": "bun build src/bin.ts --target node --minify --external bun --outfile dist/fui.js",
-    "build:bin": "bun build --compile --minify src/bin.ts --outfile dist/fui",
+    "fui": "bun run build && node dist/fui.js",
+    "build": "bun build src/bin.ts --target node --minify --outfile dist/fui.js",
     "prepack": "bun run build",
     "test": "bun test",
     "lint": "oxlint",
@@ -33,8 +32,7 @@
     "format:check": "oxfmt --check",
     "typecheck": "tsc --noEmit",
     "sync:skill": "bun scripts/sync-skill.ts",
-    "sync:upstream-tests": "bun scripts/sync-upstream-tests.ts",
-    "test:node": "bun run build && FUI_TEST_NODE=1 bun test test/cli.test.ts test/file.test.ts test/log.test.ts test/settings.test.ts test/simulate-last.test.ts"
+    "sync:upstream-tests": "bun scripts/sync-upstream-tests.ts"
   },
   "devDependencies": {
     "@fui-org/fui-mcp": "1.4.0",
@@ -53,7 +51,6 @@
     }
   },
   "engines": {
-    "bun": ">=1.4.0",
     "node": ">=22"
   }
 }

package/skills/fui/SKILL.md

@@ -58,7 +58,7 @@ description: Use the `fui` CLI for all FUI (low-code platform) work — projects
    - `fui module outline`: the layout tree (grid widths, bindings, actions, dialogs) to confirm the structure is what you meant.
    - `fui module simulate --scenario '[{"click":"Save"},{"assert":"vueData.list.length > 0"}]'`: runs the module in a simulated runtime; exit 1 when an assert fails. `--mocks` wins over live data. An unmocked static API may call the real tAPI when its local `.sql` body reads as read-only (max 8 calls, cached in `_testdata/`). For an existing SP take mocks from `fui sp verify`, never invent them. Keep scenario and mocks in files (`--scenario-file`, `--mocks-file`); `fui module simulate --last` reruns the module's last input (render mode, viewport, files) and re-reads those files. When the scenario changes a lot, pass it inline with `--last --scenario '[...]'`: one command, one step. Add `--brief` (remembered by `--last`) to print only failures, warnings, asserts, stats and screenshot paths.
    - `fui component preview <uc-name> --cases '[{"name":"empty","props":{"items":[]}}]'`: one local `.vue` alone in a real browser; do it before wiring a component in and before publishing a project-scope one.
-   - `fui module simulate --render [--device mobile]`: the real page in headless Chromium, last and only for problems that need pixels. Project-level assets come from the server, so publish project files first. It prints screenshot paths: open and read them, then fix what you see. Needs Playwright once: `bun add -g playwright && bunx playwright install chromium`.
+   - `fui module simulate --render [--device mobile]`: the real page in headless Chromium, last and only for problems that need pixels. Project-level assets come from the server, so publish project files first. It prints screenshot paths: open and read them, then fix what you see. Needs Playwright once, installed with the same package manager as fui: `npm install -g playwright && npx playwright install chromium` (or `bun add -g playwright && bunx playwright install chromium`).
 4. Publish:
    - **Whole module, including header/body:** `fui module preview` → show the changes to the user → after approval `fui module publish html --approval <token>`.
      - The token breaks if any payload file changes after the preview.
@@ -157,7 +157,7 @@ fui query "SELECT TOP 5 ID, Name FROM tblX" --json | jq -r '.[].Name'
 
 ```bash
 printf %s "$TOKEN" | fui db add docs -p lhu-docs --token - --api-domain tapi.lhu.edu.vn --user-token-env UT
-fui db add local -p demo --conn-env PG_URL        # postgres:// mysql:// sqlite:// connect directly
+fui db add local -p demo --conn-env SQLITE_URL    # sqlite:// connects directly (MSSQL goes through tAPI)
 fui db default lhu-docs/docs
 fui db test --db lhu-docs/docs
 fui token decode --db lhu-docs/docs               # never shows the password