Full-stack app

Your app serves its pages and its API from one server: Next.js with API routes and server actions, Remix, Nuxt, SvelteKit, or a plain Node server. danwo starts it, so every call it makes goes through danwo's proxy. This is the setup with the most coverage.

Set it upCopy Anchor Link

Give danwo the command that starts your app and where it answers. List the services your app calls:

import { appEnvironment, defineConfig, resendService, stripeService } from "@danwo/sdk"

export default defineConfig({
  testDir: "tests",
  environment: () =>
    appEnvironment({
      app: { command: "npm run dev", url: "http://localhost:3000" },
      services: [stripeService(), resendService()],
    }),
})

danwo runs npm run dev with its proxy settings and a test certificate. When your server calls api.stripe.com, the Stripe emulator answers. Your code doesn't change.

What you getCopy Anchor Link

Next.js: routes, edge, middleware and server actionsCopy Anchor Link

We checked Next.js 16.4.2 under both next dev and next start. These all reached the Stripe emulator through danwo's proxy:

The same app started without danwo reached the real Stripe from all four. Edge routes and middleware work because, on your machine, Next.js runs them inside its own Node server process, which danwo started.

Server actions run in that same server process, like server components, so their calls go through the proxy too.

PitfallsCopy Anchor Link

• A build that fetches during start-up. Fonts or remote config fetched at build time go through the proxy too. Pass unmatched: "passthrough" (the default) or add those hosts to allow when you block the rest. The page's own images and fonts still load under block; see Outside hosts.
• A start script that sets NODE_OPTIONS. danwo keeps its settings anyway, through a small node wrapper on the app's PATH. See Real stacks.
• Other runtimes. danwo covers Node and Bun servers. We haven't checked Deno, or wrangler dev for Cloudflare Workers, yet.

NextCopy Anchor Link