| Filename | Latest commit message | Latest commit date |
|---|---|---|
bf0e195ddcEvery production report of the board-load crash so far has been a console dump with no timing and no state, which is why five theories died slowly and none reproduced locally. This records the few facts that would actually discriminate between the ones still standing, and nothing else. Marks: fs:wait, fs:ready, stage:done, open:start, open:settled, presync:settled, ui:ready — on one monotonic clock, each carrying the wasm heap size, with growth called out explicitly. Why these: - The open window is where the crash lives: OpenProjectFiles runs the footprint library preload INLINE on the main thread in the WASM build. Bracketing it lets a crash be placed inside or outside that window instead of inferred from log order. - ui:ready is first paint. The symbolized trap needs !m_gal->IsInitialized(), so a report containing this mark rules that mechanism out and one stopping before it does not. - Heap size at every mark, because growing wasm memory detaches JS-side views, and a stale view writing into a detached buffer is one of the few mechanisms that yields a bad function-table index much later. Already earning its keep: a local Leonardo load grows 256MB -> 443MB during staging, immediately before the open. Locally that is survivable; production should not be guessed at. dump() prints the whole timeline and is wired into all three fatal paths (boot catch, window error, unhandled rejection), so one paste from a user carries the full load shape. Bounded at 200 entries; unit-tested including eviction. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0137pGo8W7asomGUTRMB7RzM |
||
| .. | ||
| backend | ||
| pcbjam-shared@0f839cda76 | ||
| standalone | ||
| .env.example | ||
| .gitignore | ||
| package.json | ||
| pnpm-lock.yaml | ||
| pnpm-workspace.yaml | ||
| README.md | ||
| tsconfig.base.json | ||
| turbo.json | ||
PCBJam Web — standalone editor (GPL)
A self-contained, GPL web app that opens KiCad projects in the WASM tools
(pcbnew / eeschema / pl_editor / …) — from a local folder, or from any backend
that implements the MIT @pcbjam/shared contract. It opens a
tool by URL:
/p/<project>/<tool>/<file-path> e.g. /p/demo/pcbnew/nyak.kicad_pcb
This workspace contains only the generic editor and a thin reference backend. All project-specific concerns (accounts, project management, uploads, auth) live in the separate closed application, which reuses this editor by hosting it standalone and redirecting to it (it must not link the GPL editor).
Layout
web/
├── standalone/ # @pcbjam/standalone — the GPL editor (Vite + React)
├── backend/ # @pcbjam/backend-example — thin reference @pcbjam/shared impl
└── pcbjam-shared/ # @pcbjam/shared — the FE↔BE contract (git submodule, MIT)
- Editor: Vite + React + TypeScript. Boots a tool directly in the document (no iframe), syncs the project tree into MEMFS, drives File→Open, and runs same-tab collaboration over BroadcastChannel.
- Example backend: Fastify + ts-rest serving a single project off the local
filesystem (
PROJECT_DIR). No DB, no auth, no uploads — the minimum the editor needs, and a worked example of the contract. Listens on:3060. Ondev/startit self-provisions example libraries — a curated slice of upstream KiCad symbol + footprint libs is cloned + extracted into.libs(served as read-only origins), so a bare clone has libraries to browse with no closed repo present. Seebackend/src/extract/.
Quick start
cd web
pnpm install
git submodule update --init web/pcbjam-shared # if not already populated
cp standalone/.env.example standalone/.env
cp backend/.env.example backend/.env # PROJECT_DIR=../../tests/fixtures/demo
pnpm dev # turbo: backend :3060 + editor :3048
Open http://localhost:3048 — either open a local folder (no backend needed)
or open the backend's project. The editor can point at any conforming backend
via VITE_API_BASE_URL.
WASM artifacts
The runtime artifacts (<tool>.js/.wasm, wx.js, images.tar.gz, <tool>.html)
are build outputs, not committed. They are synced into tests/apps/kicad/ by
tests/scripts/setup-kicad-wasm.sh (from repo-root output/).
They must be served same-origin as the app. Under the document's COEP /
cross-origin-isolation (set by the Vite dev server), KiCad WASM refuses to load
its glue/wasm from a different origin. pnpm dev runs scripts/link-wasm.mjs,
which symlinks standalone/public/wasm → tests/apps/kicad; Vite serves them
at /wasm. VITE_WASM_ASSET_BASE_URL defaults to /wasm.
- Point the symlink elsewhere with
WASM_SRC_DIR=/path pnpm --filter @pcbjam/standalone link-wasm. - If a tool won't load, the target dir is probably empty — run
tests/scripts/setup-kicad-wasm.shto populatetests/apps/kicad/. - prod: point
VITE_WASM_ASSET_BASE_URLat a URL whose origin also satisfies the same-origin / COEP constraints.
Scripts
| Command | What |
|---|---|
pnpm dev |
editor + example backend (turbo) |
pnpm build |
build all packages |
pnpm typecheck |
typecheck all packages |
Contract (@pcbjam/shared, MIT)
The editor reads from a backend over the shared contract:
GET /api/projects, GET /api/projects/:project,
GET /api/projects/:project/files, and the streamed
GET /api/projects/:project/files/* (raw bytes). Management/write operations and
ownership are not part of this contract — they belong to the closed app.