AkurAI Build
Sign in with AkurAI ID
Menu

AkurAI-Build

public

Latest change 1c2159692a31765cd66ed709791ba11468054873 - Initial commit: bunfork v0.1.0 source tree by Olafur Bui

# Official framework static-export gates

Verified on 2026-07-11 with Node 26.4.0 and npm 12.0.0. Projects and installed dependencies lived only under ignored `target/framework-e2e`; no framework source or generated asset is incorporated into Bunfork.

Each gate used the producer's official build, `bunfork admit`, `bunfork doctor`, a real Bunfork listener on a 31210+ loopback port, HTTP route/asset probes, and clean shutdown. A second gate used Playwright 1.60.0 with Chromium 148.0.7778.96 on ports 31240–31244.

| Producer | Exact packages | Admitted output | HTTP evidence |
| --- | --- | --- | --- |
| Svelte + Vite SPA | Svelte 5.56.4, Vite 8.1.4, `@sveltejs/vite-plugin-svelte` 7.1.2 | 3 files / 26,062 bytes | `/` and deep SPA route 200; JS/CSS 200; missing asset 404 |
| SvelteKit static | Kit 2.69.2, adapter-static 3.0.10, Svelte 5.56.4, Vite 8.1.4 | 15 files / 74,428 bytes | `/` and `/guide/` 200; `/guide` 308; all 12 `_app` files 200 |
| Next.js export | Next 16.3.0-canary.83, React 19.2.7 | 29 files / 642,389 bytes | `/` and `/nested/` 200; `/nested` 308; `_next` JS 200; generated 404 used |
| Vue + Vite SPA | Vue 3.5.39, Vite 8.1.4, `@vitejs/plugin-vue` 6.0.7 | 3 files / 60,290 bytes | `/` and deep SPA route 200; JS/CSS 200; missing JS 404; ETag 304 |
| Nuxt generate | Nuxt 4.3.1, nuxi 3.36.1, Nitro 2.13.4, Vue 3.5.39, build Vite 7.3.6 | 18 files / 193,127 bytes | `/` 200; nested route 308 then 200; payload/SVG/all `_nuxt` scripts 200; generated 404 status 404 |

Canonical reference commits:

- Svelte `b4d1583ae20f3869a88a731d9a265c546c099f66`
- SvelteKit `5c38e515db7fbb92e5ae01db84b4f0040a02f187`
- Next.js `1bd2fd585aac793ca2589e6f18f17a412fd11005`
- Vue `c0606e91798c8dca4f33d101e1dd836d672592c1`
- Nuxt `33f0fdb9d208355c5f76e4d56211d90b6a77c3bd`
- Vite `c961cae2868cc1521457ec60583867f0440e6949`

Representative commands:

```sh
npm install --no-audit --no-fund
npm run build       # Vite, SvelteKit, Next
npm run generate    # Nuxt

bunfork admit --artifact <output> --manifest bunfork-static.json \
  --mode <mpa|spa> [--fallback index.html] --trailing-slash <directory|ignore>
bunfork doctor --static <output> --manifest bunfork-static.json --json
bunfork serve --static <output> --manifest bunfork-static.json \
  --address 127.0.0.1:<31210+>
```

Scope is deliberately static deployment compatibility. These gates do not claim source/build compatibility, server-side JavaScript, Next standalone/RSC, SvelteKit adapter-node/actions, Vite SSR, or Nuxt/Nitro execution.

SvelteKit, Next, and Nuxt emit inline hydration/bootstrap code, so Bunfork's static CSP currently permits same-origin scripts and `'unsafe-inline'`. A stricter deployment needs build-specific CSP hashes/nonces at the trusted reverse proxy.

The Chromium gate passed all five exports. It exercised Svelte/React counters, Vue and Nuxt mounting, SvelteKit/Next/Nuxt client-side navigation, SPA fallbacks, nested deep reloads, and referenced assets. There were no console errors, page errors, failed assets, or HTTP error responses. Test projects, installed packages, generated outputs, browser binaries, the harness, and its JSON result stay under ignored `target/framework-e2e`; they are verification inputs, not shipped Bunfork code.