All Errors

This Next.js error occurs when a page file does not export a valid React component as its default export. Next.js requires every page file to export a function or class component that returns JSX.

This error occurs in Next.js when a file in the pages directory does not export a default React component. The Next.js Pages Router requires every page file to have a default export containing a valid React component.

This error occurs when attempting to render a JavaScript Symbol directly in JSX or pass it as a React child. React cannot render Symbols because they are non-serializable primitive types that have no string representation suitable for DOM rendering.

This error occurs when using the Next.js Image component without providing required width and height props for remote images. Next.js needs these dimensions to prevent layout shift and optimize image loading.

This error occurs when Node.js attempts an HTTPS connection to a server with an SSL/TLS certificate signed by a Certificate Authority (CA) that is not trusted or recognized. Node.js maintains a list of trusted root CAs, and when a certificate is signed by an unknown or self-signed CA, the connection is rejected.

Prisma Accelerate cannot connect to the database or the Accelerate API service is unreachable. This error typically stems from network connectivity issues, incorrect connection strings, firewall restrictions, or configuration problems with Prisma Accelerate setup.

This error occurs when attempting to use the fetch API without properly declaring the containing function as async. In Next.js, fetch must be called with await inside an async function, particularly in Server Components.

This error occurs when Next.js server-side renders HTML that differs from what React produces during client-side hydration. Common causes include using browser APIs, dynamic dates/times, or non-deterministic values during the initial render. The fix involves ensuring consistent rendering between server and client.

This error occurs when attempting to access a forwarded ref inside a callback or useEffect hook before the ref has been populated with the DOM element. React refs are assigned after the component mounts, causing timing issues when accessed too early.

This error occurs in Next.js when using async/await operations in a Server Component without declaring the component function as async. React Server Components require the async keyword to use await syntax.

This error occurs when TypeScript's type system prevents you from passing a 'never' type value to a function parameter, even if that parameter accepts 'any'. The 'never' type represents an impossible value, and TypeScript's variance rules prevent it from being assigned to parameters.

This error occurs when a file expected to export a React component instead exports something else, or when Fast Refresh cannot properly identify component exports. It commonly appears in Next.js pages and Vite/React projects using Fast Refresh.

SSH connections hang indefinitely during the key exchange phase, displaying the debug message 'expecting SSH2_MSG_KEX_ECDH_REPLY'. This is typically caused by network path MTU issues, firewall rules blocking fragmentation packets, or ICMP configuration problems that prevent proper key exchange negotiation.

React.createContext() requires a default value argument, but was called with no parameters. This TypeScript error occurs when createContext is invoked without providing the required defaultValue parameter.

TypeScript prevents arithmetic operations on invalid types like strings, booleans, and Date objects. This error enforces type safety by requiring operands to be number, bigint, enum, or any types.

React raises this error whenever the bundle that ends up in the browser is still running a build that predates React 18 or resolves to a different runtime than the one supplying <code>useId</code>. The hook was introduced in React 18 for stable ID generation, so any version mismatch, duplicate React resolution, or legacy CDN script that delivers React 17 causes the runtime to throw before your components render. This guide walks through the typical traps (duplicate versions, bundler aliases, cached scripts) and the steps to lock everything on React 18+ so the hook is actually available.

This error occurs when explicitly setting defaultProps to undefined in React components. While defaultProps is meant to provide fallback values for missing props, setting them to undefined defeats this purpose and can cause runtime issues.

React issues this warning when the second argument to useEffect is an object (or any non-array value) instead of a dependency array.

React throws this warning when both value and defaultValue props are specified on a form element. This happens when developers accidentally mix controlled and uncontrolled component patterns, which creates ambiguity about who manages the input state.

This error occurs when a Node.js client and server cannot establish a secure TLS/SSL connection during the handshake process. The handshake failure typically stems from protocol version mismatches, incompatible cipher suites, certificate validation issues, or misconfigured TLS settings.