hatch-surf/node_modules/next/dist/server/mcp/tools/next-instance-error-state.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

21 lines
665 B
TypeScript

/**
* Global error state for Next.js instance-level errors that are not associated
* with a specific browser session or route. This state is exposed through the MCP server's `get_errors`
* tool as well. This covers the errors that are global to the Next.js instance, such as errors in next.config.js.
*
*
* ## Usage
*
* This state is directly manipulated by various parts of the Next.js dev server:
*
* // Reset the error state
* NextInstanceErrorState.[errorType] = []
*
* // Capture an error for a specific error type
* NextInstanceErrorState.[errorType].push(err)
*
*/
export declare const NextInstanceErrorState: {
nextConfig: unknown[];
};