buildx-cli 1.8.36 → 1.8.38

package/README.md

@@ -292,6 +292,12 @@ Next.js starter behavior (`--app next`):
 - includes built-in theme mode setup (`light|dark|system`) with toggle.
 - includes built-in locale setup (`en|th`) with selector.
 - default web UI stack is HeroUI (`@heroui/react`) as primary component framework.
+- generated provider wiring does not import/wrap `HeroUIProvider` (compatibility with current HeroUI export surface).
+- generated auth wiring supports dual mode:
+  - `buildx` mode (root auth API, no project scope)
+  - `project` mode (project-scoped auth API with project id)
+  - `auto` mode (uses project id only when provided)
+- starter card layout uses `CardContent` (not `CardBody`) for current HeroUI package compatibility.
 - auth screens use shared UI pack components without forcing full-screen background, so page/layout background is controlled by the generated app.
 
 Expo starter behavior (`--app expo`):
@@ -305,6 +311,7 @@ Expo starter behavior (`--app expo`):
 - includes required `heroui-native` peer dependencies: `uniwind`, `tailwind-merge`, `tailwind-variants`, `react-native-gesture-handler`, `@gorhom/bottom-sheet`.
 - includes `react-native-worklets` dependency required by current `react-native-reanimated` chain.
 - keeps auth state split (public/private view) and uses shared Buildx auth provider wiring.
+- generated auth wiring supports dual mode (`buildx|project|auto`) with project-id forwarding on auth actions.
 - includes starter auth flows on mobile:
   - sign-in (username/password)
   - sign-up (name/email/tel support)
@@ -350,6 +357,11 @@ Generated auth-aware structure:
   - public screen tree for unauthenticated users
   - private screen tree for authenticated users
   - mobile-first baseline with `heroui-native` provider
+- Generated auth mode env defaults:
+  - `NEXT_PUBLIC_BUILDX_AUTH_MODE` / `EXPO_PUBLIC_BUILDX_AUTH_MODE` / `VITE_BUILDX_AUTH_MODE` (default: `auto`)
+  - `NEXT_PUBLIC_BUILDX_PROJECT_ID` / `EXPO_PUBLIC_BUILDX_PROJECT_ID` / `VITE_BUILDX_PROJECT_ID` used as default project scope in `project` mode
+  - in `project` mode, generated auth forms pass `projectId` explicitly to auth actions
+  - in `buildx` mode, generated auth provider forces root scope (no project id)
 - Scaffold layout is single-level:
   - app package files are generated at workspace root (no `apps/web` nesting)
   - `buildx/` artifacts are generated at root level alongside app files
@@ -364,25 +376,61 @@ UI package dependency resolution:
 Notes:
 - Next scaffold requires npm registry connectivity for `create-next-app`.
 - Use `--dry-run` to preview file plan without running scaffold commands.
+- After backend bootstrap, `project:init` automatically runs initial pull via CLI:
+  - `schema:pull --target-dir <workspace>/buildx/generated`
+  - `function:pull --target-dir <workspace>/buildx`
+  - `ai-function:pull --target-dir <workspace>/buildx/ai-functions`
+  - `template:pull --target-dir <workspace>/buildx/templates`
+  so starter artifact docs/structure are available immediately.
 - Generated projects are package-manager agnostic (no forced `packageManager` lock in generated `package.json`).
 - Next `app/globals.css` is normalized with Tailwind `@source` to include UI pack classes from `node_modules` (prevents missing utilities like `grid-cols-2` from shared components).
 - Next starter includes `@heroui/react` by default.
 - Expo starter includes `heroui-native` by default.
 
-### New Project Maintenance
+### Standard Artifact Guideline
 
-After `project:init`, use these commands to maintain local/remote artifact parity:
+Use this as the standard workflow for project artifacts after `project:init`.
+
+Scope and location:
+- schema artifacts: `buildx/generated/*`
+- function artifacts: `buildx/functions/*`
+- AI function artifacts: `buildx/ai-functions/*`
+- template artifacts: `buildx/templates/*`
+
+Initial sync baseline:
+- `project:init` auto-pulls all artifact groups (`schema`, `function`, `ai-function`, `template`).
+
+Daily standard loop (recommended):
+1. Pull latest remote artifacts first.
+2. Edit local files.
+3. Diff against remote.
+4. Push with `--dry-run`.
+5. Push for real after review.
 
 ```bash
-# schema lifecycle
+# 1) pull latest (all artifact groups)
 npx buildx-cli schema:pull --project-id <project-id>
-npx buildx-cli schema:diff --project-id <project-id>
-npx buildx-cli schema:push --project-id <project-id> --dry-run
-
-# function lifecycle
 npx buildx-cli function:pull --project-id <project-id>
+npx buildx-cli ai-function:pull --project-id <project-id>
+npx buildx-cli template:pull --project-id <project-id>
+
+# 2) diff before push
+npx buildx-cli schema:diff --project-id <project-id> --details
 npx buildx-cli function:diff --project-id <project-id>
+npx buildx-cli ai-function:diff --project-id <project-id>
+npx buildx-cli template:diff --project-id <project-id>
+
+# 3) dry-run push
+npx buildx-cli schema:push --project-id <project-id> --dry-run
 npx buildx-cli function:push --project-id <project-id> --dry-run
+npx buildx-cli ai-function:push --project-id <project-id> --dry-run
+npx buildx-cli template:push --project-id <project-id> --dry-run
+
+# 4) push for real
+npx buildx-cli schema:push --project-id <project-id>
+npx buildx-cli function:push --project-id <project-id>
+npx buildx-cli ai-function:push --project-id <project-id>
+npx buildx-cli template:push --project-id <project-id>
 ```
 
 ### Users
@@ -553,6 +601,10 @@ Field annotations (JSDoc in `types.ts`) are supported:
 - `@bx.validate <json_or_string>`
 - `@bx.props <json-object>` (merge custom keys into `propertiesScheme`)
 
+Required behavior:
+- converter does not auto-assume `required: true` from non-optional TypeScript syntax by default.
+- use `@bx.required` (or `@bx.required false`) for explicit required control.
+
 System-managed fields:
 - `createdAt`, `updatedAt`, `createdBy`, `updatedBy` in `types.ts` are ignored by convert output and never synced back
 

package/dist/README.md

@@ -292,6 +292,12 @@ Next.js starter behavior (`--app next`):
 - includes built-in theme mode setup (`light|dark|system`) with toggle.
 - includes built-in locale setup (`en|th`) with selector.
 - default web UI stack is HeroUI (`@heroui/react`) as primary component framework.
+- generated provider wiring does not import/wrap `HeroUIProvider` (compatibility with current HeroUI export surface).
+- generated auth wiring supports dual mode:
+  - `buildx` mode (root auth API, no project scope)
+  - `project` mode (project-scoped auth API with project id)
+  - `auto` mode (uses project id only when provided)
+- starter card layout uses `CardContent` (not `CardBody`) for current HeroUI package compatibility.
 - auth screens use shared UI pack components without forcing full-screen background, so page/layout background is controlled by the generated app.
 
 Expo starter behavior (`--app expo`):
@@ -305,6 +311,7 @@ Expo starter behavior (`--app expo`):
 - includes required `heroui-native` peer dependencies: `uniwind`, `tailwind-merge`, `tailwind-variants`, `react-native-gesture-handler`, `@gorhom/bottom-sheet`.
 - includes `react-native-worklets` dependency required by current `react-native-reanimated` chain.
 - keeps auth state split (public/private view) and uses shared Buildx auth provider wiring.
+- generated auth wiring supports dual mode (`buildx|project|auto`) with project-id forwarding on auth actions.
 - includes starter auth flows on mobile:
   - sign-in (username/password)
   - sign-up (name/email/tel support)
@@ -350,6 +357,11 @@ Generated auth-aware structure:
   - public screen tree for unauthenticated users
   - private screen tree for authenticated users
   - mobile-first baseline with `heroui-native` provider
+- Generated auth mode env defaults:
+  - `NEXT_PUBLIC_BUILDX_AUTH_MODE` / `EXPO_PUBLIC_BUILDX_AUTH_MODE` / `VITE_BUILDX_AUTH_MODE` (default: `auto`)
+  - `NEXT_PUBLIC_BUILDX_PROJECT_ID` / `EXPO_PUBLIC_BUILDX_PROJECT_ID` / `VITE_BUILDX_PROJECT_ID` used as default project scope in `project` mode
+  - in `project` mode, generated auth forms pass `projectId` explicitly to auth actions
+  - in `buildx` mode, generated auth provider forces root scope (no project id)
 - Scaffold layout is single-level:
   - app package files are generated at workspace root (no `apps/web` nesting)
   - `buildx/` artifacts are generated at root level alongside app files
@@ -364,25 +376,61 @@ UI package dependency resolution:
 Notes:
 - Next scaffold requires npm registry connectivity for `create-next-app`.
 - Use `--dry-run` to preview file plan without running scaffold commands.
+- After backend bootstrap, `project:init` automatically runs initial pull via CLI:
+  - `schema:pull --target-dir <workspace>/buildx/generated`
+  - `function:pull --target-dir <workspace>/buildx`
+  - `ai-function:pull --target-dir <workspace>/buildx/ai-functions`
+  - `template:pull --target-dir <workspace>/buildx/templates`
+  so starter artifact docs/structure are available immediately.
 - Generated projects are package-manager agnostic (no forced `packageManager` lock in generated `package.json`).
 - Next `app/globals.css` is normalized with Tailwind `@source` to include UI pack classes from `node_modules` (prevents missing utilities like `grid-cols-2` from shared components).
 - Next starter includes `@heroui/react` by default.
 - Expo starter includes `heroui-native` by default.
 
-### New Project Maintenance
+### Standard Artifact Guideline
 
-After `project:init`, use these commands to maintain local/remote artifact parity:
+Use this as the standard workflow for project artifacts after `project:init`.
+
+Scope and location:
+- schema artifacts: `buildx/generated/*`
+- function artifacts: `buildx/functions/*`
+- AI function artifacts: `buildx/ai-functions/*`
+- template artifacts: `buildx/templates/*`
+
+Initial sync baseline:
+- `project:init` auto-pulls all artifact groups (`schema`, `function`, `ai-function`, `template`).
+
+Daily standard loop (recommended):
+1. Pull latest remote artifacts first.
+2. Edit local files.
+3. Diff against remote.
+4. Push with `--dry-run`.
+5. Push for real after review.
 
 ```bash
-# schema lifecycle
+# 1) pull latest (all artifact groups)
 npx buildx-cli schema:pull --project-id <project-id>
-npx buildx-cli schema:diff --project-id <project-id>
-npx buildx-cli schema:push --project-id <project-id> --dry-run
-
-# function lifecycle
 npx buildx-cli function:pull --project-id <project-id>
+npx buildx-cli ai-function:pull --project-id <project-id>
+npx buildx-cli template:pull --project-id <project-id>
+
+# 2) diff before push
+npx buildx-cli schema:diff --project-id <project-id> --details
 npx buildx-cli function:diff --project-id <project-id>
+npx buildx-cli ai-function:diff --project-id <project-id>
+npx buildx-cli template:diff --project-id <project-id>
+
+# 3) dry-run push
+npx buildx-cli schema:push --project-id <project-id> --dry-run
 npx buildx-cli function:push --project-id <project-id> --dry-run
+npx buildx-cli ai-function:push --project-id <project-id> --dry-run
+npx buildx-cli template:push --project-id <project-id> --dry-run
+
+# 4) push for real
+npx buildx-cli schema:push --project-id <project-id>
+npx buildx-cli function:push --project-id <project-id>
+npx buildx-cli ai-function:push --project-id <project-id>
+npx buildx-cli template:push --project-id <project-id>
 ```
 
 ### Users
@@ -553,6 +601,10 @@ Field annotations (JSDoc in `types.ts`) are supported:
 - `@bx.validate <json_or_string>`
 - `@bx.props <json-object>` (merge custom keys into `propertiesScheme`)
 
+Required behavior:
+- converter does not auto-assume `required: true` from non-optional TypeScript syntax by default.
+- use `@bx.required` (or `@bx.required false`) for explicit required control.
+
 System-managed fields:
 - `createdAt`, `updatedAt`, `createdBy`, `updatedBy` in `types.ts` are ignored by convert output and never synced back