| Filename | Latest commit message | Latest commit date |
|---|---|---|
9c475a804e
The runtime is JSPI-only; this removes everything that still pretended otherwise. Three exhaustive sweeps (C++/JS+build+CI/tests+docs) drove the inventory; every deletion verified by grep closure + full gates. Broken-right-now fixes: - deploy-staging.yml passed the retired opt_level input — the workflow could not even start. Removed. - env.sh carried dead exports with a live -sASYNCIFY=1 inside (WASM_LDFLAGS/PTHREAD_LDFLAGS, zero consumers). Removed; the WASM_LEGACY_EXCEPTIONS rationale rewritten to the real reason. - docker/build.sh exported PCBJAM_ASYNC_BACKEND (read nowhere). Gone. Dead weight removed: - binaryen submodule (nothing builds or invokes it), wasm-opt-bench workflow + scripts/bench/, get-wasm-opt.sh, diagnostics.js (242 lines of Asyncify-API-only code), the KICAD_PIPELINE background-postprocess scaffolding (existed to parallelize the deleted wasm-opt phase; the postprocess is a seconds-long node script and now runs inline), build-monitor's dead asyncify rows, sched-context orphan build output, dead .gitignore entries, the .jspi-assets spike dir (the two wf-result research JSONs moved to docs/features/async/migration-evidence/). - bindings: fiber_park.h + its 12 embind registrations (broken-if- called under JSPI), the kicadOpenFileStart/OPEN_JOB starter route, main_stack_runner.h + 5 includes, the always-null context-sleep weak hook in nanosleep_yield.c. - shim: the backend field (installed-flag idempotency instead), noteContextWait (dead both sides), the __wxAsyncifyDump alias (+ the WasmTool fallback and string-dump normalize branch). - web: the emscripten-6-ignored mainScriptUrlOrBlob option in boot.ts (gerber-demo keeps it: it loads the deployed CDN release, which predates emscripten 6 — noted inline). Conditionals: all 'backend === jspi' checks reduced to scheduler- presence checks; races_quiescent re-keyed from Asyncify.state (vacuous) to real backlog quiescence (resumeReady/mutatorQueue — NOT _windowLive, which is the probing activation's own window by definition). Renames (identifiers only, no file renames): ASYNC_LINK_FLAGS→ JSPI_LINK_FLAGS and Makefile ASYNC_LDFLAGS→JSPI_LDFLAGS, kicadCollabFiberBusy→kicadCollabBusy (embind + web + tests), collab_common.h fiber*→apply*/coroutine naming, asyncifySignatures→ wasmTrapSignatures (lists byte-identical). Tests: the two remaining vacuous [wx-asyncify]/fiber-resume-refused asserts re-keyed to live JSPI beacons; eeschema-load's failure message no longer sends the developer to a deleted script; wait-beacons' dead families/parser deleted; lane-0 legacy-glue guards removed (lane 0 is unconstructible); the embind test.fail re-gated with the JSPI reason (plain embind invokers cannot suspend — verified still failing); lint-determinism now scans tests/jspi (166 files clean); eeschema-collab local-move gated to chromium (~50% flaky on FF even solo; pcbnew twin covers both engines). Docs: DEBUG.md rewritten as the JSPI debugging guide; build.md describes the single-phase build; docs/features/async/README.md banner-marked historical and repointed at the NEW 23-jspi-runtime.md (current architecture: export census, turnstile, libcontext ownership + refusal contract, embind call shapes, the em-pthread service-wrapper trick, exception policy, known gaps). Gates on the cleaned tree: test:e2e 725 passed / 0 failed (after the quiescence-probe fix; the 3 other reds were verified contention flakes solo-green or the documented FF gate), web 76/0, jspi 18/18 both engines, vitest 295/295 + 17/17, all lints green, live-app census clean. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016X9eh1s5sTx1o9Em9KBuwR |
||
| .. | ||
| brand | ||
| functions | ||
| public | ||
| src | ||
| test | ||
| .dev.vars.example | ||
| .gitignore | ||
| astro.config.mjs | ||
| package-lock.json | ||
| package.json | ||
| postcss.config.mjs | ||
| README.md | ||
| tsconfig.json | ||
| vitest.config.ts | ||
| wrangler.toml | ||
site
Public-facing marketing/content site for the KiCad WebAssembly project: landing page, blog, and legal pages. Built with Astro 6.
This is a standalone project — it is intentionally decoupled from the /web
app monorepo (which is the product itself: React frontend + Fastify backend).
It uses npm (not the monorepo's pnpm) and has its own package-lock.json.
What it ships
- Static by default: every page is prerendered to HTML and ships zero client JavaScript. A visitor downloads HTML + CSS only — no React/JS bundle.
- No adapter and no server bundle: the build emits
dist/only. The single dynamic endpoint,/api/waitlist, ships as a Cloudflare Pages Function fromfunctions/(see below).
Routes
| Route | Source |
|---|---|
/ |
src/pages/index.astro |
/blog |
src/pages/blog/index.astro |
/blog/<id> |
src/pages/blog/[slug].astro |
/terms |
src/pages/terms.astro |
/privacy |
src/pages/privacy.astro |
/cookies |
src/pages/cookies.astro |
Blog posts are Markdown files in src/content/blog/, validated by the schema in
src/content.config.ts. Add a post by dropping a new .md file there with
title, description, and pubDate frontmatter.
Local development
Requires Node ≥ 22.12 (Astro 6 requirement).
cd site
npm install
npm run dev # http://localhost:4321
npm run build # outputs to dist/ (static only — no adapter)
npm run preview # serve the production build locally
Dynamic routes
Every page is static. The one server-side endpoint is a Cloudflare Pages Function, not an Astro SSR route:
functions/api/waitlist.ts -> POST/OPTIONS/GET /api/waitlist
Pages maps the functions/ tree to routes by path, and the handlers are named
exports (onRequestPost, onRequestOptions, onRequestGet). Config arrives on
context.env, not via astro:env/server. public/_routes.json restricts
Function invocation to /api/*, so every page and asset stays a plain static
request.
To add another endpoint, drop a new file in functions/ — no Astro adapter and
no prerender = false involved.
Locally, run the built site the way Pages will serve it (this is the only way to
exercise the Function, astro dev does not run functions/):
cp .dev.vars.example .dev.vars # fill in as needed; gitignored
npm run build
npm run pages:dev # http://localhost:8788
Deploying
www.pcbjam.com is a Cloudflare Pages project (pcbjam-site), deployed by
.github/workflows/deploy-site.yml on every push to main touching site/** —
content and blog posts do not wait for a release tag.
push to main (site/**) -> npm ci -> npm test -> astro build
-> wrangler pages deploy -> www.pcbjam.com
Two things live outside the repo and are set once:
- Secrets —
wrangler pages secret put <NAME> --project-name pcbjam-siteforRESEND_API_KEY,RESEND_SEGMENT_ID,WAITLIST_FROM_EMAIL.WAITLIST_ALLOWED_ORIGINSis deliberately unset; it keeps the in-code default. - The custom domain — attached to the Pages project (there is no
wrangler pages domainsubcommand). The apexpcbjam.com308s towwwvia a Cloudflare Redirect Rule.
Response headers come from public/_headers (copied verbatim into dist/), which
carries the COOP/COEP rules the embedded Gerber viewer needs. Do not widen
them to /* — the landing page must stay un-isolated so the YouTube hero embed
loads.
One-time setup, the invariants that fail silently if changed, and the health
check (deploy/site/verify.sh) are in ../deploy/site/README.md.