buildx-cli 1.8.21 → 1.8.22
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +10 -0
- package/dist/README.md +10 -0
- package/dist/index.cjs +1 -1
- package/dist/index.js +1 -1
- package/dist/package.json +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -255,12 +255,18 @@ npx buildx-cli project:init --project-id hello-world --name "Hello World" --app
|
|
|
255
255
|
```
|
|
256
256
|
|
|
257
257
|
Generated auth-aware structure:
|
|
258
|
+
- Next.js scaffold source:
|
|
259
|
+
- `project:init --app next` runs `npx create-next-app@latest` first (TypeScript + App Router)
|
|
260
|
+
- then applies Buildx auth/public-private route wiring and maintenance scripts
|
|
258
261
|
- Next.js template uses route groups for separation:
|
|
259
262
|
- `app/(public)/...` (sign-in/sign-up/forgot-password)
|
|
260
263
|
- `app/(private)/...` (protected dashboard)
|
|
261
264
|
- Expo template uses auth-state route split in `App.tsx`:
|
|
262
265
|
- public screen tree for unauthenticated users
|
|
263
266
|
- private screen tree for authenticated users
|
|
267
|
+
- Scaffold layout is single-level:
|
|
268
|
+
- app package files are generated at workspace root (no `apps/web` nesting)
|
|
269
|
+
- `buildx/` artifacts are generated at root level alongside app files
|
|
264
270
|
|
|
265
271
|
UI package dependency resolution:
|
|
266
272
|
- generated apps depend on package from env `BUILDX_UI_PACKS_PACKAGE`
|
|
@@ -268,6 +274,10 @@ UI package dependency resolution:
|
|
|
268
274
|
- set a scoped package before seeding when unscoped npm name is unavailable:
|
|
269
275
|
- `BUILDX_UI_PACKS_PACKAGE=@your-scope/buildx-react-ui-packs npx buildx-cli project:init ...`
|
|
270
276
|
|
|
277
|
+
Notes:
|
|
278
|
+
- Next scaffold requires npm registry connectivity for `create-next-app`.
|
|
279
|
+
- Use `--dry-run` to preview file plan without running scaffold commands.
|
|
280
|
+
|
|
271
281
|
### New Project Maintenance
|
|
272
282
|
|
|
273
283
|
After `project:init`, use these commands to maintain local/remote artifact parity:
|
package/dist/README.md
CHANGED
|
@@ -255,12 +255,18 @@ npx buildx-cli project:init --project-id hello-world --name "Hello World" --app
|
|
|
255
255
|
```
|
|
256
256
|
|
|
257
257
|
Generated auth-aware structure:
|
|
258
|
+
- Next.js scaffold source:
|
|
259
|
+
- `project:init --app next` runs `npx create-next-app@latest` first (TypeScript + App Router)
|
|
260
|
+
- then applies Buildx auth/public-private route wiring and maintenance scripts
|
|
258
261
|
- Next.js template uses route groups for separation:
|
|
259
262
|
- `app/(public)/...` (sign-in/sign-up/forgot-password)
|
|
260
263
|
- `app/(private)/...` (protected dashboard)
|
|
261
264
|
- Expo template uses auth-state route split in `App.tsx`:
|
|
262
265
|
- public screen tree for unauthenticated users
|
|
263
266
|
- private screen tree for authenticated users
|
|
267
|
+
- Scaffold layout is single-level:
|
|
268
|
+
- app package files are generated at workspace root (no `apps/web` nesting)
|
|
269
|
+
- `buildx/` artifacts are generated at root level alongside app files
|
|
264
270
|
|
|
265
271
|
UI package dependency resolution:
|
|
266
272
|
- generated apps depend on package from env `BUILDX_UI_PACKS_PACKAGE`
|
|
@@ -268,6 +274,10 @@ UI package dependency resolution:
|
|
|
268
274
|
- set a scoped package before seeding when unscoped npm name is unavailable:
|
|
269
275
|
- `BUILDX_UI_PACKS_PACKAGE=@your-scope/buildx-react-ui-packs npx buildx-cli project:init ...`
|
|
270
276
|
|
|
277
|
+
Notes:
|
|
278
|
+
- Next scaffold requires npm registry connectivity for `create-next-app`.
|
|
279
|
+
- Use `--dry-run` to preview file plan without running scaffold commands.
|
|
280
|
+
|
|
271
281
|
### New Project Maintenance
|
|
272
282
|
|
|
273
283
|
After `project:init`, use these commands to maintain local/remote artifact parity:
|