hatch-surf/node_modules/next/dist/server/node-environment-extensions/unhandled-rejection.external.d.ts
Riley Zhang df378d33ef
Some checks failed
CI / go (push) Waiting to run
CI / docker (push) Waiting to run
CI / lint-go (push) Waiting to run
CI / lint-docs (push) Waiting to run
CI / check-paperclip (push) Waiting to run
Deploy static site / Deploy to GitHub Pages (push) Has been cancelled
Deploy static site / Deploy via Docker to hatch.surf (push) Has been cancelled
Merge GitHub main into Gitea repo (allow unrelated histories)
Resolved conflicts by taking GitHub versions for:
- .dockerignore, .gitignore, Dockerfile, README.md, docker-compose.yml

Kept deploy.sh updated to:
- Pull from GitHub (primary source)
- Push to Gitea (push-mirror)
- Build from site/ directory (GitHub structure)

Co-Authored-By: Paperclip <noreply@paperclip.ing>
2026-06-25 05:20:46 +02:00

22 lines
998 B
TypeScript

/**
* Manages unhandled rejection listeners to intelligently filter rejections
* from aborted prerenders when cache components are enabled.
*
* THE PROBLEM:
* When we abort prerenders we expect to find numerous unhandled promise rejections due to
* things like awaiting Request data like `headers()`. The rejections are fine and should
* not be construed as problematic so we need to avoid the appearance of a problem by
* omitting them from the logged output.
*
* THE STRATEGY:
* 1. Install a filtering unhandled rejection handler
* 2. Intercept process event methods to capture new handlers in our internal queue
* 3. For each rejection, check if it comes from an aborted prerender context
* 4. If yes, suppress it. If no, delegate to all handlers in our queue
* 5. This provides precise filtering without time-based windows
*
* This ensures we suppress noisy prerender-related rejections while preserving
* normal error logging for genuine unhandled rejections.
*/
export {};