Netlify

Netlify gives you two runtime options for an API: Edge Functions (Deno-based, global) and Functions v2 (Node, fetch-style). Both speak the web-standard Request → Responsecontract, so the DaloyJS adapter is the same helper in both places — only the file location and the optional config export change.

When to choose Netlify

You want a platform-managed REST API with Edge or Node function options.
You want preview deploys per branch with zero config.
You're fine with platform-managed cold starts.

Netlify Edge Functions (Deno)

Edge Functions run on a Deno-based runtime. Use toWebHandler— the same helper as the Vercel Edge adapter, because the input/output shape is identical.

// netlify/edge-functions/api.ts
import { toWebHandler } from "@daloyjs/core/vercel";
import type { Config } from "@netlify/edge-functions";
import { app } from "../../src/server.ts";

export default toWebHandler(app);

export const config: Config = {
  path: "/api/*",
};

Netlify Functions v2 (Node, fetch-style)

Functions v2 is GA and is the recommended way to write Node functions on Netlify. The old v1 lambda-style handler (exports.handler = (event, context) => ...) is legacy — it still works for compatibility but you should write new code in v2.

// netlify/functions/api.mts
import { toWebHandler } from "@daloyjs/core/vercel";
import type { Config } from "@netlify/functions";
import { app } from "../../src/server.js";

export default toWebHandler(app);

export const config: Config = {
  path: "/api/*",
};

If you have an existing v1 codebase you can't migrate yet, the Lambda adapter still works against the v1 event shape:

// netlify/functions/api.ts (legacy v1 — only if you can't move to v2)
import { toLambdaHandler } from "@daloyjs/core/lambda";
import { app } from "../../src/server.js";

export const handler = toLambdaHandler(app);

netlify.toml

For a REST-API-only project there is no static site to publish. Omit the publishkey (or point it at an empty directory) so Netlify doesn't try to serve your compiled server code as static files.

toml

[build]
  command = "pnpm build"

[functions]
  node_bundler = "esbuild"

# only needed if you don't use the config export above
[[edge_functions]]
  function = "api"
  path = "/api/*"

Deploy

bash

pnpm netlify dev
pnpm netlify deploy --build
pnpm netlify deploy --build --prod

Gotchas

Edge Functions don't expose node:*— same caveat as Vercel Edge and Cloudflare Workers.
Functions v2 returns a Responsedirectly. Don't use the v1 statusCode/body object shape in v2 code.
context.waitUntil is available in v2 for fire-and-forget work.

Search docs