cursedops 0.10.20 → 0.10.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/package.json +1 -1
- package/src/serve.ts +3 -0
- package/src/workerDeploy.ts +19 -1
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "cursedops",
|
|
3
|
-
"version": "0.10.
|
|
3
|
+
"version": "0.10.22",
|
|
4
4
|
"description": "The build-and-ops answers this generation's apps wrote independently and identically: finding a generation's roots — and printing a command that runs when pasted — without knowing a path, the generation's whole-tree laws run over one repo from a checkout or a worktree, macOS launchd agent install/replace/remove and the live port a job serves, the scaffolding and verdicts of a deployed smoke (origin probe, the smoke's own environment, a network that lies about DNS, a settled version), the static-serving helpers eight apps copied — the path-traversal guard among them — the API floor that keeps an unmatched /api/... from ever being answered with the app shell, the commit and dirty flag a checkout-served process reports, the Cloudflare Worker deploy toolkit four apps copied (the deploy sequence, exact-set secrets over a pipe, origin-first rollback, the curl edge fetch, the row-for-row D1 import proof, the billed-CPU tail check around a deploy's walk and smoke, and each app's worker:secrets and worker:smoke main as one function of its data), the relay a Worker fronts a Mac-bound app with (the Durable Object, the frames, the Mac's dialer and key rotation — lifted from station for roms — and the signed-in stage walk's skeleton and the relay app's whole worker:deploy), the Worker import-graph and await-port checks every Worker app's suite runs over its own source, and the public-surface ratchet three published libraries each carried a forked copy of. Mechanism only — no app knows its name from here. Bun, zero runtime dependencies (typescript is an optional peer, for public-surface only), ships source.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"scripts": {
|
package/src/serve.ts
CHANGED
|
@@ -82,6 +82,9 @@ const CONTENT_TYPES: Readonly<Record<string, string>> = {
|
|
|
82
82
|
woff2: "font/woff2",
|
|
83
83
|
txt: "text/plain; charset=utf-8",
|
|
84
84
|
map: "application/json; charset=utf-8",
|
|
85
|
+
// A Vite build emits `.wasm` for an imported `?url` module. Browsers refuse
|
|
86
|
+
// `WebAssembly.instantiateStreaming` on anything but this type (task 2217).
|
|
87
|
+
wasm: "application/wasm",
|
|
85
88
|
};
|
|
86
89
|
|
|
87
90
|
/** The `content-type` for a path, by extension — `application/octet-stream` if unknown. */
|
package/src/workerDeploy.ts
CHANGED
|
@@ -33,7 +33,9 @@
|
|
|
33
33
|
* 1. **a readable HEAD** — nothing to stamp is nothing that could prove the deploy;
|
|
34
34
|
* 2. **a clean tree for production** — a dirty one would report one commit and run another;
|
|
35
35
|
* 3. **the app's own refusals** (data) — e.g. its Mac host still loaded while the config routes
|
|
36
|
-
* the hostname to the Worker: two writers, two databases;
|
|
36
|
+
* the hostname to the Worker: two writers, two databases; then **`node_modules` made to
|
|
37
|
+
* match `bun.lock`** ({@link INSTALL}) — a bundle built from stale modules runs code the
|
|
38
|
+
* stamped commit does not name;
|
|
37
39
|
* 4. **the STAGE first, for production** — `collections` went live 2026-09-22 with every anonymous
|
|
38
40
|
* check green and its owner unable to sign in; the stage walk is what found why, and a step
|
|
39
41
|
* in the sequence is one a person in a hurry cannot skip;
|
|
@@ -490,6 +492,9 @@ export function judgeSchemaApply(code: number, stdout: string): { applied: boole
|
|
|
490
492
|
* Run the sequence in the header's order, stopping at the first red with a sentence. Never
|
|
491
493
|
* exits — the caller does, with {@link DeployResult.code}.
|
|
492
494
|
*/
|
|
495
|
+
/** What {@link runWorkerDeploy} runs first: `node_modules` exactly as `bun.lock` says. */
|
|
496
|
+
export const INSTALL: readonly string[] = ["bun", "install", "--frozen-lockfile"];
|
|
497
|
+
|
|
493
498
|
export function runWorkerDeploy(spec: WorkerDeploySpec, deps: DeployDeps): DeployResult {
|
|
494
499
|
const log = deps.log ?? ((line: string) => console.log(line));
|
|
495
500
|
const error = deps.error ?? ((line: string) => console.error(line));
|
|
@@ -523,6 +528,19 @@ export function runWorkerDeploy(spec: WorkerDeploySpec, deps: DeployDeps): Deplo
|
|
|
523
528
|
const why = wrangler ? sameZoneFetchRefusal(wrangler, env) : null;
|
|
524
529
|
if (why) return stop("same-zone", `${why} Nothing was deployed.`);
|
|
525
530
|
}
|
|
531
|
+
/*
|
|
532
|
+
* 🔴 Built in, never an app's to remember: `node_modules` is made to match `bun.lock` before
|
|
533
|
+
* anything builds or bundles (wrangler bundles `worker/` from it too, so `--no-build` needs it
|
|
534
|
+
* as much as a build does). A fast-forward that moves `bun.lock` does not touch
|
|
535
|
+
* `node_modules`, and on 2026-09-28 vault's deploy of a commit locking cursedbelt 5.15.2 built
|
|
536
|
+
* and shipped 5.14.0 from disk — the `/healthz` commit said one thing and the bundle ran
|
|
537
|
+
* another, the exact lie the clean-tree refusal exists to prevent. `--frozen-lockfile` is a
|
|
538
|
+
* no-op when they already agree, and refuses, rather than rewriting the lock, when they cannot.
|
|
539
|
+
*/
|
|
540
|
+
step("make node_modules match bun.lock");
|
|
541
|
+
if (deps.run(INSTALL, {}) !== 0) {
|
|
542
|
+
return stop("install", `\`${INSTALL.join(" ")}\` failed — node_modules cannot be made to match bun.lock, so nothing was built or deployed.`);
|
|
543
|
+
}
|
|
526
544
|
if (spec.env === "production") {
|
|
527
545
|
for (const command of spec.stageFirst ?? []) {
|
|
528
546
|
step(`the stage first — production waits on it: ${command.join(" ")}`);
|