buildx-cli 1.8.23 → 1.8.25

package/README.md

@@ -236,6 +236,7 @@ Key options:
 - `--react-stack <vite|next|expo-web>`: required when `--app react`
 - `--out-dir <path>`: output workspace directory (default `./<project-id>`)
 - `--overwrite`: allow writing into non-empty output directory
+- `--use-existing`: allow using existing `project_id` without creating a new backend project
 - `--dry-run`: compute output without writing files or calling APIs
 - `--json`: print machine-readable result
 
@@ -256,6 +257,42 @@ npx buildx-cli project:init --project-id hello-world --name "Hello World" --app
 
 # backend + Expo app
 npx buildx-cli project:init --project-id hello-world --name "Hello World" --app expo
+
+# existing backend project id (reuse backend, scaffold local files)
+npx buildx-cli project:init --project-id hello-world --name "Hello World" --app next --use-existing
+```
+
+Existing project behavior:
+- CLI checks existing project IDs before create.
+- If `project_id` already exists:
+  - interactive mode asks for confirmation to continue with existing backend.
+  - with `--use-existing`, CLI skips confirmation and continues directly.
+  - with `--json` and no `--use-existing`, CLI exits with error (no interactive prompt in JSON mode).
+
+Next.js starter behavior (`--app next`):
+- public/private route split remains (`app/(public)` and `app/(private)`).
+- root app shell includes a reusable navbar.
+- includes built-in theme mode setup (`light|dark|system`) with toggle.
+- includes built-in locale setup (`en|th`) with selector.
+- auth screens use shared UI pack components without forcing full-screen background, so page/layout background is controlled by the generated app.
+
+#### `project:add-pack`
+Add Buildx pack dependencies into an existing project package.
+
+Key options:
+- `--pack <ui-packs|sdk>`: pack to install
+- `--version <version>`: optional version override
+- `--dir <path>`: target project directory (default current directory)
+- `--manager <bun|pnpm|npm|yarn>`: force package manager
+- `--json`: print machine-readable result
+
+Examples:
+```bash
+# add UI packs with default version
+npx buildx-cli project:add-pack --pack ui-packs
+
+# add sdk in specific directory with pnpm
+npx buildx-cli project:add-pack --pack sdk --manager pnpm --dir ./my-project
 ```
 
 Generated auth-aware structure:
@@ -265,6 +302,8 @@ Generated auth-aware structure:
 - Next.js template uses route groups for separation:
   - `app/(public)/...` (sign-in/sign-up/forgot-password)
   - `app/(private)/...` (protected dashboard)
+  - preserves create-next-app root `app/layout.tsx` (no hard overwrite)
+  - starter root `app/page.tsx` includes generic `Dashboard`, `Sign in`, and `Sign up` links with usage description
 - Expo template uses auth-state route split in `App.tsx`:
   - public screen tree for unauthenticated users
   - private screen tree for authenticated users
@@ -275,12 +314,15 @@ Generated auth-aware structure:
 UI package dependency resolution:
 - generated apps depend on package from env `BUILDX_UI_PACKS_PACKAGE`
 - default package name is `buildx-react-ui-packs`
+- default package version is `^1.8.3` (override via `BUILDX_UI_PACKS_VERSION`)
 - set a scoped package before seeding when unscoped npm name is unavailable:
   - `BUILDX_UI_PACKS_PACKAGE=@your-scope/buildx-react-ui-packs npx buildx-cli project:init ...`
 
 Notes:
 - Next scaffold requires npm registry connectivity for `create-next-app`.
 - Use `--dry-run` to preview file plan without running scaffold commands.
+- 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).
 
 ### New Project Maintenance
 

package/dist/README.md

@@ -236,6 +236,7 @@ Key options:
 - `--react-stack <vite|next|expo-web>`: required when `--app react`
 - `--out-dir <path>`: output workspace directory (default `./<project-id>`)
 - `--overwrite`: allow writing into non-empty output directory
+- `--use-existing`: allow using existing `project_id` without creating a new backend project
 - `--dry-run`: compute output without writing files or calling APIs
 - `--json`: print machine-readable result
 
@@ -256,6 +257,42 @@ npx buildx-cli project:init --project-id hello-world --name "Hello World" --app
 
 # backend + Expo app
 npx buildx-cli project:init --project-id hello-world --name "Hello World" --app expo
+
+# existing backend project id (reuse backend, scaffold local files)
+npx buildx-cli project:init --project-id hello-world --name "Hello World" --app next --use-existing
+```
+
+Existing project behavior:
+- CLI checks existing project IDs before create.
+- If `project_id` already exists:
+  - interactive mode asks for confirmation to continue with existing backend.
+  - with `--use-existing`, CLI skips confirmation and continues directly.
+  - with `--json` and no `--use-existing`, CLI exits with error (no interactive prompt in JSON mode).
+
+Next.js starter behavior (`--app next`):
+- public/private route split remains (`app/(public)` and `app/(private)`).
+- root app shell includes a reusable navbar.
+- includes built-in theme mode setup (`light|dark|system`) with toggle.
+- includes built-in locale setup (`en|th`) with selector.
+- auth screens use shared UI pack components without forcing full-screen background, so page/layout background is controlled by the generated app.
+
+#### `project:add-pack`
+Add Buildx pack dependencies into an existing project package.
+
+Key options:
+- `--pack <ui-packs|sdk>`: pack to install
+- `--version <version>`: optional version override
+- `--dir <path>`: target project directory (default current directory)
+- `--manager <bun|pnpm|npm|yarn>`: force package manager
+- `--json`: print machine-readable result
+
+Examples:
+```bash
+# add UI packs with default version
+npx buildx-cli project:add-pack --pack ui-packs
+
+# add sdk in specific directory with pnpm
+npx buildx-cli project:add-pack --pack sdk --manager pnpm --dir ./my-project
 ```
 
 Generated auth-aware structure:
@@ -265,6 +302,8 @@ Generated auth-aware structure:
 - Next.js template uses route groups for separation:
   - `app/(public)/...` (sign-in/sign-up/forgot-password)
   - `app/(private)/...` (protected dashboard)
+  - preserves create-next-app root `app/layout.tsx` (no hard overwrite)
+  - starter root `app/page.tsx` includes generic `Dashboard`, `Sign in`, and `Sign up` links with usage description
 - Expo template uses auth-state route split in `App.tsx`:
   - public screen tree for unauthenticated users
   - private screen tree for authenticated users
@@ -275,12 +314,15 @@ Generated auth-aware structure:
 UI package dependency resolution:
 - generated apps depend on package from env `BUILDX_UI_PACKS_PACKAGE`
 - default package name is `buildx-react-ui-packs`
+- default package version is `^1.8.3` (override via `BUILDX_UI_PACKS_VERSION`)
 - set a scoped package before seeding when unscoped npm name is unavailable:
   - `BUILDX_UI_PACKS_PACKAGE=@your-scope/buildx-react-ui-packs npx buildx-cli project:init ...`
 
 Notes:
 - Next scaffold requires npm registry connectivity for `create-next-app`.
 - Use `--dry-run` to preview file plan without running scaffold commands.
+- 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).
 
 ### New Project Maintenance