saqib mirandClaude Sonnet 5
95b5a1e03d
Configures both previously-empty test runners (vitest.config.ts, playwright.config.ts) and adds the typed lib/api client layer (axios + interceptors), the session-cookie plumbing (lib/auth), TanStack Query infrastructure (lib/query, providers), and a real sign-in flow consuming supporthub-api's own login (010-identity-auth) - the true foundation every other user story in this feature depends on. Two structural fixes to the existing scaffold, both found only by running the app rather than by inspection: middleware.ts belongs at src/middleware.ts under this project's src/ layout, not the repo root; and next.config.mjs's output:'export' is incompatible with Next.js Middleware outright (the dev server refuses to start it), so this app now runs as a standard Next.js server - confirmed with the user before making that deployment-mode change. Verified end-to-end with a real, locally-running supporthub-api: all 5 Playwright scenarios (unauthenticated redirect, sign-in, wrong-password generic error, non-admin role gating, sign-out) pass against a live backend, not a mock. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
10 lines
398 B
JavaScript
10 lines
398 B
JavaScript
/** @type {import('next').NextConfig} */
|
|
const nextConfig = {
|
|
// 001-agent-admin-ui: static export ('output: export') is incompatible with Next.js
|
|
// Middleware, which the (support)/(admin) portals' sign-in guard requires (FR-000) — this app
|
|
// now runs as a standard Next.js server (`next build && next start`), not a static export.
|
|
reactStrictMode: true,
|
|
};
|
|
|
|
export default nextConfig;
|