package.json

{
  "name": "website",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "eslint",
    "typecheck": "tsc --noEmit",
    "gen:api": "openapi-ts && pnpm gen:ws",
    "gen:ws": "node scripts/gen-ws-events.mjs"
  },
  "dependencies": {
    "@radix-ui/react-dialog": "^1.1.23",
    "@radix-ui/react-dropdown-menu": "^2.1.24",
    "@radix-ui/react-popover": "^1.1.23",
    "@radix-ui/react-select": "^2.3.7",
    "@radix-ui/react-switch": "^1.3.7",
    "@radix-ui/react-tabs": "^1.1.21",
    "@radix-ui/react-tooltip": "^1.2.16",
    "@tanstack/react-query": "^5.101.4",
    "embla-carousel-react": "^8.6.0",
    "embla-carousel-wheel-gestures": "^8.1.0",
    "lucide-react": "^1.28.0",
    "next": "16.3.0",
    "react": "19.2.8",
    "react-dom": "19.2.8",
    "react-hot-toast": "^2.6.0",
    "zustand": "^5.0.14"
  },
  "//dependencyCaps": "eslint stays on 9 and typescript on 5 because of the ecosystem, not by choice. eslint 10 breaks eslint-plugin-react (pulled in by eslint-config-next): it calls a context API v10 removed, so a lint run dies before reporting anything. typescript 7 is refused outright by typescript-eslint — only 8.66.1-alpha supports it — which takes the lint step with it. Retry both when eslint-config-next ships an eslint-10 plugin set and typescript-eslint 9 is stable.",
  "devDependencies": {
    "@hey-api/openapi-ts": "^0.99.0",
    "@playwright/test": "^1.62.1",
    "@tailwindcss/postcss": "^4.3.3",
    "@types/node": "^24.10.1",
    "@types/react": "^19.2.18",
    "@types/react-dom": "^19.2.4",
    "eslint": "^9.39.5",
    "eslint-config-next": "16.3.0",
    "tailwindcss": "^4.3.3",
    "typescript": "^5.9.3",
    "yaml": "^2.9.0"
  }
}