Files
the-sunken-reach/package.json
T
joshuaandClaude Opus 5.5 7b3d121151 V1.12.3: live updates behind any proxy, fewer requests
- Live updates start on plain requests and move up to a websocket when
  one gets through. The site used to ask for the websocket first, with
  no way back: behind a proxy that does not pass the upgrade, nothing
  live arrived at all.
- A browser asks the API's leave before a request, the site and the API
  being on different hosts. It now remembers the answer for two hours,
  where it used to ask before nearly every request.
- A built file is kept by the browser for good: its name changes when
  its contents do. Each used to be checked again on every page load.
- For a real websocket through nginx, the blocks that pass requests to
  the API need "proxy_http_version 1.1", "proxy_set_header Upgrade
  $http_upgrade" and "proxy_set_header Connection "upgrade"".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-08 21:04:45 +02:00

32 lines
766 B
JSON

{
"name": "dnd-campaign-manager",
"version": "1.12.3",
"private": true,
"description": "D&D 5e campaign manager — monorepo root",
"workspaces": [
"backend",
"frontend"
],
"scripts": {
"dev:backend": "npm run dev --workspace backend",
"dev:frontend": "npm run dev --workspace frontend",
"test:backend": "npm run test --workspace backend",
"seeds:check": "npm run seeds:check --workspace backend"
},
"allowScripts": {
"prisma": true,
"@prisma/client": true,
"@prisma/engines": true,
"bcrypt": true,
"@parcel/watcher": false,
"unrs-resolver": false
},
"overrides": {
"mysql2": "^3.24.5",
"deepmerge-ts": "^8.0.2",
"@istanbuljs/load-nyc-config": {
"js-yaml": "^4.1.0"
}
}
}