@coxmos/adapter-edge

SvelteKit adapter targeting coxmos-edge's Deno-isolate runtime.

Not yet confirmed — flagged directly in files/entry.js:

• The exact glue between builder.generateManifest()'s output and SvelteKit's internal Server class (import path, Server#init() signature, Server#respond()'s second-argument shape). This was reconstructed from public patterns, not fetched line-for-line from adapter-node's actual internal wiring.

Usage

npm install @coxmos/adapter-edge

// svelte.config.js
import adapter from '@coxmos/adapter-edge';

export default {
	kit: {
		adapter: adapter({
			out: '.coxmos/edge' // optional, this is the default
		})
	}
};

npm run build

Output

.coxmos/edge/
├── client/              # static assets (from builder.writeClient)
├── server/
│   └── manifest.js       # from builder.generateManifest()
├── entry.js              # Deno fetch-handler entrypoint (see caveats above)
└── coxmos-manifest.json  # RouteManifest, same shape as coxmos-build-cli's other framework outputs

Verification checklist

Run through this before trusting the build output:

1. npm run build completes without errors.
2. .coxmos/edge/entry.js exists and .coxmos/edge/server/manifest.js exists.
3. Inspect manifest.js — confirm it exports something named manifest (or update the import in entry.js to match whatever it actually exports).
4. Try running entry.js under Deno directly and hit it with a real request — if Server#init or Server#respond throw, that confirms the unverified glue needs adjusting; the error message will tell you the real expected signature.
5. Only after a real request gets a real response should this be considered working.