crashscope

"fix(server): build crashscope-core before next build on Vercel The Vercel build was failing with "Module not found: Can't resolve '@pradhankukiran/crashscope-core'" because pnpm symlinks the workspace package (link-workspace-packages=true in .npmrc), but the symlink target's dist/ is never built — and the package's exports point at ./dist/*.js. Prepend `pnpm --filter @pradhankukiran/crashscope-core build` to the server's build script so dist/ exists before next build resolves the import. Works the same on Railway (Dockerfile builds the workspace explicitly already, so this is just a no-op extra build step there)."

Branch: master

"fix(server): repoint broken Railway button + add a Render card Railway's /new/template?template=<github-url> URL pattern silently 404s — that endpoint expects a Railway-internal published template id, not a GitHub URL. Repoint the Railway button at /new (the project picker) and rename to 'Open Railway' since it's no longer one-click. Add Render as a fourth deploy target. Render's /deploy?repo=<github-url> URL DOES support one-click deploys from any GitHub repo — it picks up the Dockerfile automatically. Grid widens from 3 cards to 4 (2-up on small screens, 4-up on lg)."

Branch: master

"feat(server): vercel deploy support (conditional config + npm-resolvable dep)"

Branch: master

"feat(server): vercel deploy support (conditional config + npm-resolvable dep) Two changes to make the same Next.js app deploy cleanly on Vercel in addition to Railway: 1. packages/server/package.json — switch the @pradhankukiran/crashscope-core dep from 'workspace:*' to '^0.1.1'. Locally pnpm still uses the workspace symlink via link-workspace-packages=true in .npmrc, but Vercel (which uploads only packages/server) can now resolve the published version from npm. Railway already resolves via the Dockerfile that copies the whole monorepo, so unaffected. 2. packages/server/next.config.mjs — gate the standalone-output bits (output: 'standalone' + experimental.outputFileTracingRoot) behind '!process.env.VERCEL'. On Vercel, both produce a doubled /vercel/path0/vercel/path0/... path that breaks the build; Vercel has its own serverless packaging and doesn't need standalone. Docker/Railway still get the same output as before. Also ignore the .vercel/ project link directory at the serv"

Branch: master

Manual Deployment

Manual Deployment

Manual Deployment