@crustjs/crust-windows-arm64 0.5.3 → 0.5.5

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.
@@ -1,4 +1,4 @@
1
1
  [diffend] Oversized file quarantined before diffing.
2
2
  name: package/bin/crust-bun-windows-arm64.exe
3
- size: 77745664 bytes
4
- sha256: cd16399f4ea7d1e905f3e544d1fc31398cd683a1938c7559cd105222e8a51d79
3
+ size: 77745152 bytes
4
+ sha256: 5f64f9337b97aeeab855413f233d5f2e026c846e3e81ca4ecc758d0a7efbd346
@@ -1,6 +1,5 @@
1
1
  import { BuildReport, BuildReport as BuildReport$1 } from "@crustjs/core";
2
- import "@crustjs/core/tooling";
3
- //#region src/utils/distribute.d.ts
2
+ //#region src/distribute.d.ts
4
3
  /**
5
4
  * What one build distributes: a runtime `package` (a root-only JavaScript
6
5
  * bundle that needs the runtime installed) or standalone `binary` executables
@@ -33,7 +32,7 @@ type BuildArtifact = {
33
32
  command: string;
34
33
  };
35
34
  //#endregion
36
- //#region src/commands/build.d.ts
35
+ //#region src/build.d.ts
37
36
  /** Options of the programmatic {@link build}; `crust build` maps its flags onto them. */
38
37
  type BuildOptions = {
39
38
  /** Project root whose package.json `bin` and `crust` are read. Default: `process.cwd()`. */
@@ -74,12 +73,13 @@ type BuildResult = {
74
73
  * `bin` entry, each the command's bundle (artifact `package`) or a Node
75
74
  * launcher (artifact `binary`), plus for binaries one platform package per
76
75
  * target holding one executable per command. Command names and source entries
77
- * come from `bin`; the runtime, artifact, Bun plugins, and extra directories
78
- * from package.json `crust`. Bundling and Command Snapshots run in bun
79
- * subprocesses (bun on PATH, or the running Bun executable), so this works
80
- * under Node as well when Bun is installed; Deno binaries and Deno runtime
81
- * packages (experimental, deno 2.5.0 or newer) need deno on PATH, and Node
82
- * binaries a node on PATH that Crust's tsdown can build executables with.
76
+ * come from `bin`; the runtime, artifact, Bun plugins, extra directories, and
77
+ * external dependencies from package.json `crust`. Bundling and Command
78
+ * Snapshots run in bun subprocesses (bun on PATH, or the running Bun
79
+ * executable), so this works under Node as well when Bun is installed; Deno
80
+ * binaries and Deno runtime packages (experimental, deno 2.5.0 or newer) need
81
+ * deno on PATH, and Node binaries a node on PATH that Crust's tsdown can build
82
+ * executables with.
83
83
  *
84
84
  * Throws on any failure. Planning and compiler-selection failures (bad
85
85
  * options or package.json, a missing or hung compiler, an engines mismatch) leave the