create-crust 0.0.21 → 0.0.23

package/README.md

@@ -23,7 +23,23 @@ Every generated project includes:
 - `README.md` — getting started instructions
 - `.gitignore` — sensible defaults for Node/Bun projects
 
-Generated templates can be configured for either standalone binary distribution (`bin` -> `dist/cli`, `files: ["dist"]`) or Bun runtime package distribution (`bin` -> `dist/cli.js`, runtime deps) during scaffolding. Standalone binaries are the recommended default.
+Generated templates can be configured for either standalone binary distribution or Bun runtime package distribution during scaffolding.
+
+For standalone binary projects, the intended workflow is:
+
+1. `bun run build` — raw binaries (`crust build`)
+2. `bun run package` — npm-ready staged packages in `dist/npm` (`crust build --package`)
+3. `bun run publish` — publish the staged packages (`crust publish`)
+
+The binary templates intentionally keep `build` and `package` as separate scripts because they do different jobs:
+
+- `build` is for raw binary artifacts.
+- `package` is for npm packaging (alias for `crust build --package`).
+- `publish` is for registry upload.
+
+If you need public build-time constants, `crust build` can use Bun's cwd env by default or explicit `--env-file` inputs.
+
+> **Note:** The template's top-level `package.json` has `"files": ["dist"]` and `"bin"` pointing to `dist/cli` for local development. When publishing via `crust publish`, the staged packages in `dist/npm/` each have their own `package.json` with the correct `files` and `bin` entries — the top-level fields are not used for npm distribution.
 
 ## Documentation
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "create-crust",
-	"version": "0.0.21",
+	"version": "0.0.23",
 	"description": "Scaffold a new Crust CLI project.",
 	"type": "module",
 	"license": "MIT",
@@ -37,10 +37,11 @@
 		"build": "bunup",
 		"dev": "bunup --watch",
 		"check:types": "tsc --noEmit",
-		"test": "bun test"
+		"test": "bun test",
+		"publish": "bun publish --no-git-checks || true"
 	},
 	"dependencies": {
-		"@crustjs/core": "0.0.13",
+		"@crustjs/core": "0.0.14",
 		"@crustjs/create": "0.0.4",
 		"@crustjs/prompts": "0.0.9"
 	},

package/templates/distribution/binary/package.json

@@ -4,7 +4,9 @@
 	"type": "module",
 	"description": "A CLI built with Crust",
 	"files": [
-		"dist"
+		"dist/cli",
+		"dist/cli.cmd",
+		"dist/*-bun-*"
 	],
 	"bin": {
 		"{{name}}": "dist/cli"
@@ -12,7 +14,8 @@
 	"scripts": {
 		"dev": "bun run src/cli.ts",
 		"build": "crust build",
-		"prepack": "bun run build",
+		"package": "crust build --package",
+		"publish": "crust publish --stage-dir dist/npm",
 		"start": "./dist/cli",
 		"check:types": "tsc --noEmit"
 	},

package/templates/minimal/README.md

@@ -17,12 +17,15 @@ bun run build
 
 This template supports two distribution modes:
 
-- **Standalone binaries (recommended)**: compile with `crust build` and publish `dist/` only.
+- **Standalone binaries (recommended)**: use `bun run build` for raw binaries, then `bun run package` for npm-ready staged packages.
 - **Bun runtime package**: distribute with runtime dependencies (`@crustjs/core` and `@crustjs/plugins` in `dependencies`).
 
 ## Publishing
 
-- **Standalone binaries**: keep `files: ["dist"]`, `bin` -> `dist/cli`, and use `prepack` (`bun run build`).
+- **Standalone binaries**:
+  `bun run build` produces raw binaries.
+  `bun run package` stages npm packages in `dist/npm/`.
+  `bun run publish` publishes the staged packages in manifest order.
 - **Bun runtime package**: keep `bin` -> `dist/cli.js`, build with Bun (`bun build ... --outfile dist/cli.js`), and keep runtime deps in `dependencies`.
 
 ## Usage

package/templates/modular/README.md

@@ -19,12 +19,15 @@ bun run build
 
 This template supports two distribution modes:
 
-- **Standalone binaries (recommended)**: compile with `crust build` and publish `dist/` only.
+- **Standalone binaries (recommended)**: use `bun run build` for raw binaries, then `bun run package` for npm-ready staged packages.
 - **Bun runtime package**: distribute with runtime dependencies (`@crustjs/core` and `@crustjs/plugins` in `dependencies`).
 
 ## Publishing
 
-- **Standalone binaries**: keep `files: ["dist"]`, `bin` -> `dist/cli`, and use `prepack` (`bun run build`).
+- **Standalone binaries**:
+  `bun run build` produces raw binaries.
+  `bun run package` stages npm packages in `dist/npm/`.
+  `bun run publish` publishes the staged packages in manifest order.
 - **Bun runtime package**: keep `bin` -> `dist/cli.js`, build with Bun (`bun build ... --outfile dist/cli.js`), and keep runtime deps in `dependencies`.
 
 ## Usage