- the session cookie was Secure whenever NODE_ENV=production, so a production build on http://localhost got no cookie back in Safari: every page after signup looked signed-out. It is now Secure only when X-Forwarded-Proto says https, or when COOKIE_SECURE=1. - /app and /app/[id] now require an analyst and a Jev key, the same rule /api/analyze enforces with a 412. Closing the guide mid-way used to leave a console that could not run anything. - Playwright runs the production server (pree2e builds first) and gains a webkit project for session survival; chromium-only QA could never see a Secure-cookie rejection. - tests-e2e/session.spec.ts pins both; .env.example gains COOKIE_SECURE and stops shipping a blank APP_SECRET. - e2e: 21 passed (setup, chromium, webkit, mobile). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
33 lines
799 B
JSON
33 lines
799 B
JSON
{
|
|
"name": "sql-server-qai",
|
|
"version": "0.1.0",
|
|
"private": true,
|
|
"scripts": {
|
|
"dev": "next dev",
|
|
"build": "next build",
|
|
"start": "next start",
|
|
"lint": "eslint",
|
|
"test": "node --no-warnings --test tests/*.test.ts",
|
|
"e2e": "playwright test",
|
|
"pree2e": "npm run build"
|
|
},
|
|
"dependencies": {
|
|
"@openuidev/lang-core": "^0.3.0",
|
|
"@openuidev/react-lang": "^0.3.0",
|
|
"@typesafe-ai/sdk": "^0.6.0",
|
|
"fast-xml-parser": "^5.7.3",
|
|
"next": "16.3.5",
|
|
"react": "19.2.8",
|
|
"react-dom": "19.2.8",
|
|
"zod": "^4.6.5"
|
|
},
|
|
"devDependencies": {
|
|
"@playwright/test": "^1.63.0",
|
|
"@types/node": "^24.13.6",
|
|
"@types/react": "^19",
|
|
"@types/react-dom": "^19",
|
|
"eslint": "^9",
|
|
"eslint-config-next": "16.3.5",
|
|
"typescript": "^5"
|
|
}
|
|
} |