All Errors

This error occurs when your application makes too many requests to Supabase Auth or Management API within a short timeframe, triggering built-in rate limiting that returns a 429 status code.

The Node.js domain module is deprecated and should not be used in new code. This warning appears when you import or use the domain module. Use async_hooks or AsyncResource instead for proper async context tracking.

This error occurs when Express.static() middleware is configured to serve files from a directory that doesn't exist. The application fails to start because the specified path cannot be found on the filesystem.

React throws this error when a `<Suspense>` boundary never catches a Promise or an async child, so the runtime refuses to render the boundary or its fallback.

This Fastify error occurs when you attempt to send a response twice on the same request. Once reply.send() has been called, the response is finalized and cannot be sent again. Ensure each route handler sends a response only once.

React throws this parser error when it tries to JSON.parse() a response that is actually HTML, which usually happens because the front-end asset server (webpack dev server or CRA proxy) answers the request instead of your API.

This error occurs in Fastify when you try to register a decorator (plugin, hook, or utility method) with a name that already exists. Fastify prevents duplicate decorator registration to avoid silent overwrites. The fix involves checking for existing decorators, using unique names, or explicitly overwriting when intentional.

The FST_ERR_HOOK_TIMEOUT error occurs when a Fastify hook (onRequest, onSend, etc.) takes longer than the allowed timeout to complete. This error indicates that your hook is either performing long-running operations or is stuck in an infinite loop. Resolving this requires optimizing the hook code or adjusting timeout configuration.

The react-hooks/exhaustive-deps rule warns when values used inside useMemo aren't listed in the dependency array, which causes the memoized result to become stale as props or state change.

This error occurs when a client makes a request to an Express server for a URL path that does not match any defined routes. Express returns a 404 Not Found HTTP status code, indicating the requested resource could not be found on the server.

This error occurs when fs.mkdir() or fs.mkdirSync() attempts to create a directory at a path where a file already exists. Node.js cannot create a directory with the same name as an existing file, causing the operation to fail with EEXIST.

React complains when an input starts with no value (uncontrolled) and later receives a value prop. Keeping inputs consistently controlled or using defaultValue avoids the warning and keeps form state predictable.

This error occurs when Node.js attempts to create a symbolic link on Windows without administrator privileges. Windows restricts symlink creation to admin accounts or users with specific developer mode permissions. The error commonly appears when using fs.symlink() or tools that auto-link dependencies, especially in development environments or CI/CD pipelines.

This warning occurs during React hydration when server-rendered HTML contains attributes that the client-side code doesn't expect. In older React versions (pre-16), data-reactroot and data-reactid were internal attributes used by React. Modern React has removed these attributes, but the warning can still appear due to browser extensions or version mismatches.

This error occurs when an HTTP/2 frame payload exceeds the maximum allowed frame size limit. HTTP/2 enforces strict frame size constraints (default 16KB), and this error indicates the server or client sent a frame that violates these limits, preventing the connection from continuing.

This error occurs when an HTTP/2 connection violates flow control rules by sending more data than the peer is willing to accept. Flow control in HTTP/2 prevents overwhelming the receiver by using a window-based system. The error happens when the sender exceeds the advertised window size or improperly manages window updates, causing the protocol to abort the connection.

This error occurs when apt detects that a package dependency requires a specific minimum version, but apt is attempting to install a different (usually lower) version. It indicates a version mismatch between what a package needs and what is available to install, preventing the installation from proceeding.

This error occurs when Node.js HTTP/2 session receives a SETTINGS frame that does not comply with HTTP/2 protocol specifications. The settings frame may contain invalid parameter IDs, out-of-range values, or malformed data that the HTTP/2 parser cannot process.

Express session middleware fails when the session store is not properly initialized or configured. This error occurs when express-session cannot establish a connection to the session storage backend (Memory, Redis, MongoDB, etc.). The application needs a compatible session store middleware to persist user sessions across requests.

This error occurs when Express cannot locate the view engine you specified in your application. It typically happens when the view engine package is not installed, the engine name is misspelled, or the engine is not properly registered.