Make analytics track route resilient to non-request runtimes (after() fallback)

[Copilot]

The quality Actions job failed because analytics integration tests invoke POST /api/track outside a Next.js request scope, where after() throws (next-dynamic-api-wrong-context). This change keeps deferred writes in real request contexts while preserving route behavior in test/non-request execution.

• Root cause

  • frontend/app/api/track/route.ts unconditionally called after(async () => ...).
  • In Vitest route invocation, this raised and failed analytics contract tests.

• Route hardening

  • Extracted persistence logic into a single persistAnalytics function.
  • Wrapped scheduling in try/catch:
    • request scope: after(persistAnalytics) (existing latency behavior preserved)
    • non-request scope: await persistAnalytics() fallback

• Behavioral impact

  • No schema/contract changes to analytics payload validation.
  • No changes to tracking response shape ({ ok: true, recorded: events.length }).

const persistAnalytics = async () => {
  // visitor/session/event writes
};

try {
  after(persistAnalytics);
} catch {
  await persistAnalytics();
}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
arch-draw	Ready	Preview	Aug 6, 2026 10:04am