create-crust 0.0.22 → 0.0.24

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.
Files changed (5) hide show
  1. package/README.md +5 -3
  2. package/package.json +2 -2
  3. package/templates/distribution/binary/package.json +1 -1
  4. package/templates/minimal/README.md +2 -2
  5. package/templates/modular/README.md +2 -2
package/README.md CHANGED
@@ -28,15 +28,17 @@ Generated templates can be configured for either standalone binary distribution
28
28
  For standalone binary projects, the intended workflow is:
29
29
 
30
30
  1. `bun run build` — raw binaries (`crust build`)
31
- 2. `bun run distribute` — npm-ready staged packages in `dist/npm` (`crust build --distribute`)
31
+ 2. `bun run package` — npm-ready staged packages in `dist/npm` (`crust build --package`)
32
32
  3. `bun run publish` — publish the staged packages (`crust publish`)
33
33
 
34
- The binary templates intentionally keep `build` and `distribute` as separate scripts because they do different jobs:
34
+ The binary templates intentionally keep `build` and `package` as separate scripts because they do different jobs:
35
35
 
36
36
  - `build` is for raw binary artifacts.
37
- - `distribute` is for npm packaging (alias for `crust build --distribute`).
37
+ - `package` is for npm packaging (alias for `crust build --package`).
38
38
  - `publish` is for registry upload.
39
39
 
40
+ If you need public build-time constants, `crust build` can use Bun's cwd env by default or explicit `--env-file` inputs.
41
+
40
42
  > **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.
41
43
 
42
44
  ## Documentation
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "create-crust",
3
- "version": "0.0.22",
3
+ "version": "0.0.24",
4
4
  "description": "Scaffold a new Crust CLI project.",
5
5
  "type": "module",
6
6
  "license": "MIT",
@@ -41,7 +41,7 @@
41
41
  "publish": "bun publish --no-git-checks || true"
42
42
  },
43
43
  "dependencies": {
44
- "@crustjs/core": "0.0.13",
44
+ "@crustjs/core": "0.0.15",
45
45
  "@crustjs/create": "0.0.4",
46
46
  "@crustjs/prompts": "0.0.9"
47
47
  },
package/templates/distribution/binary/package.json CHANGED
@@ -14,7 +14,7 @@
14
14
  "scripts": {
15
15
  "dev": "bun run src/cli.ts",
16
16
  "build": "crust build",
17
- "distribute": "crust build --distribute",
17
+ "package": "crust build --package",
18
18
  "publish": "crust publish --stage-dir dist/npm",
19
19
  "start": "./dist/cli",
20
20
  "check:types": "tsc --noEmit"
package/templates/minimal/README.md CHANGED
@@ -17,14 +17,14 @@ bun run build
17
17
 
18
18
  This template supports two distribution modes:
19
19
 
20
- - **Standalone binaries (recommended)**: use `bun run build` for raw binaries, then `bun run distribute` for npm-ready staged packages.
20
+ - **Standalone binaries (recommended)**: use `bun run build` for raw binaries, then `bun run package` for npm-ready staged packages.
21
21
  - **Bun runtime package**: distribute with runtime dependencies (`@crustjs/core` and `@crustjs/plugins` in `dependencies`).
22
22
 
23
23
  ## Publishing
24
24
 
25
25
  - **Standalone binaries**:
26
26
  `bun run build` produces raw binaries.
27
- `bun run distribute` stages npm packages in `dist/npm/`.
27
+ `bun run package` stages npm packages in `dist/npm/`.
28
28
  `bun run publish` publishes the staged packages in manifest order.
29
29
  - **Bun runtime package**: keep `bin` -> `dist/cli.js`, build with Bun (`bun build ... --outfile dist/cli.js`), and keep runtime deps in `dependencies`.
30
30
 
package/templates/modular/README.md CHANGED
@@ -19,14 +19,14 @@ bun run build
19
19
 
20
20
  This template supports two distribution modes:
21
21
 
22
- - **Standalone binaries (recommended)**: use `bun run build` for raw binaries, then `bun run distribute` for npm-ready staged packages.
22
+ - **Standalone binaries (recommended)**: use `bun run build` for raw binaries, then `bun run package` for npm-ready staged packages.
23
23
  - **Bun runtime package**: distribute with runtime dependencies (`@crustjs/core` and `@crustjs/plugins` in `dependencies`).
24
24
 
25
25
  ## Publishing
26
26
 
27
27
  - **Standalone binaries**:
28
28
  `bun run build` produces raw binaries.
29
- `bun run distribute` stages npm packages in `dist/npm/`.
29
+ `bun run package` stages npm packages in `dist/npm/`.
30
30
  `bun run publish` publishes the staged packages in manifest order.
31
31
  - **Bun runtime package**: keep `bin` -> `dist/cli.js`, build with Bun (`bun build ... --outfile dist/cli.js`), and keep runtime deps in `dependencies`.
32
32