Frontend and backend

Your frontend and your API are separate apps: a React or Vue frontend and a Node API, perhaps with a background worker. danwo starts all of them, in order, behind one proxy. You get the same coverage as a full-stack app.

Set it upCopy Anchor Link

List each app with its start command and address. dependsOn says what must be up first, and env hands one app another's address:

import { clerkService, defineConfig, stackEnvironment, stripeService } from "@danwo/sdk"

export default defineConfig({
  testDir: "tests",
  environment: () =>
    stackEnvironment({
      baseUrl: "web",
      services: [stripeService(), clerkService()],
      apps: [
        {
          name: "api",
          command: "npm run dev --prefix api",
          url: "http://127.0.0.1:4000",
          ready: { path: "/health" },
        },
        {
          name: "web",
          command: "npm run dev --prefix web",
          url: "http://127.0.0.1:3000",
          dependsOn: ["api"],
          env: (urls) => ({ VITE_API_URL: urls.api ?? "" }),
        },
      ],
    }),
})

danwo starts the API and waits for /health to answer. Then it starts the web app, with VITE_API_URL pointing at the API.

baseUrl names the app the browser opens. Without it, tests open the first app listed.

What you getCopy Anchor Link

• Both sides of every provider emulated. Give both apps the Clerk emulator's keys, and the browser signs in with the emulator while the API checks the token against it. The two agree.
• Faults on the frontend's calls to the API, as well as on the API's calls to providers and its database.
• Background work. Add inngestService() and settle() waits for jobs the API started.

PitfallsCopy Anchor Link

• Ports. Each app needs a fixed address, so run one worker per machine, or give each worker its own ports.
• Start-up time. A large API can take a minute to boot. Raise timeoutMs on that app.
• Calls that skip the proxy. A Node WebSocket client that ignores proxy settings (the ws package, for example) needs a proxy agent. Browser sockets always go through.

NextCopy Anchor Link