Update to Domino Data Lab

{
  "description": "Diagnose and fix Domino reverse-proxy and routing problems in published web apps by checking vite.config.js, package.json, and app.sh for wrong ports, localhost binding, absolute base paths, missing SPA fallback, or missing build steps. Use when a Domino app shows connection refused, 404s on CSS/JS assets, a blank page, or broken deep links.",
  "included_files": [],
  "name": "domino-debug-proxy",
  "skill_md_contents": "---\nname: domino-debug-proxy\ndescription: Diagnose and fix Domino reverse-proxy and routing problems in published web apps by checking vite.config.js, package.json, and app.sh for wrong ports, localhost binding, absolute base paths, missing SPA fallback, or missing build steps. Use when a Domino app shows connection refused, 404s on CSS/JS assets, a blank page, or broken deep links.\n---\n\n# Debug Domino App Proxy Issues\n\nFind the configuration mistakes that break apps behind Domino's reverse proxy, report them, and\nfix them with the user's agreement.\n\n## Steps\n\n1. Locate the app's config files: `vite.config.js`/`vite.config.ts`, `package.json`, `app.sh`,\n   and any framework entry point (`app.py`, `server.js`).\n2. Run every check below and record each result as pass or fail.\n3. Print a report in the format shown under \"Report format\".\n4. List the recommended fixes and ask whether to apply them. Apply only what the user approves.\n5. For anything you can't fix from config, give the manual investigation steps.\n\n## Checks\n\n| # | Check | Pass condition |\n|---|---|---|\n| 1 | Port | The server listens on `8888`; Vite also sets `strictPort: true` |\n| 2 | Base path | Vite sets `base: './'`; other frameworks use relative asset paths |\n| 3 | Host binding | The server binds to `0.0.0.0`, not `localhost` or `127.0.0.1` |\n| 4 | `app.sh` | It `cd`s to the code directory, runs the build, and then serves the output |\n| 5 | SPA fallback | Static serving uses `npx serve -s dist` (the `-s` flag) |\n| 6 | Asset references | No hardcoded root-absolute paths such as `/assets/...` or `fetch('/api/...')` |\n\n## Common issues\n\n| Symptom | Cause | Fix |\n|---|---|---|\n| Connection refused | Wrong port, for example 3000 | `server: { port: 8888, strictPort: true }` |\n| 404 on CSS/JS files | `base` is `/` or missing | `base: './'` in `defineConfig` |\n| App unreachable from the browser | Bound to localhost | `server: { host: '0.0.0.0' }` |\n| Deep links return 404 | `serve` without `-s` | `npx serve -s dist -l 8888` |\n| Blank page or stale content | `app.sh` has no build step | Add `npm run build` before `serve` |\n\nA corrected `app.sh` for a Vite app:\n\n```bash\n#!/bin/bash\nset -e\ncd /mnt/code\nnpm ci\nnpm run build\nnpx serve -s dist -l 8888\n```\n\n## Report format\n\n```\nDomino Proxy Debug Report\n=========================\n\nChecking: vite.config.js\n✅ Port: 8888\n✅ Base path: './'\n✅ Host: 0.0.0.0\n\nChecking: app.sh\n✅ Working directory: /mnt/code\n✅ Build command: npm run build\n❌ Serve command missing -s flag\n\nSummary: 1 issue found\n\nRecommended fixes:\n1. Update the app.sh serve command:\n   - Current: npx serve dist -l 8888\n   + Fixed:   npx serve -s dist -l 8888\n```\n\n## Manual investigation\n\nIf the config is correct but the app still fails:\n\n1. Open the browser developer tools console and look for failed module or asset loads.\n2. In the Network tab, check whether failing requests drop the app's proxy URL prefix (the part\n   of the path before the app's own routes).\n3. Check the app logs on the app's page in Domino.\n4. Confirm the app was republished after the last code change.\n\nFor general deployment guidance, use the `domino-apps` skill.\n"
}