All Errors

Event listeners added in useEffect without proper dependency handling can trap state values in stale closures, preventing component updates from being recognized and causing UI updates to fail.

TypeScript cannot locate or read your tsconfig.json file. This occurs when the configuration file is missing, in the wrong location, contains invalid JSON, or when the working directory is incorrect.

This error occurs when React detects that your component calls a different number of hooks between renders, violating the Rules of Hooks. Most commonly caused by conditional hook calls or early return statements before all hooks have been called.

This React warning appears when a forwardRef render function does not accept both props and ref as parameters. React requires forwardRef components to explicitly accept both parameters, even if the ref is not used.

React.Fragment is a special component that can only receive key and children as props. Passing any other props like className, style, or custom attributes will trigger this validation warning.

This error occurs when accessing ref.current before the ref is initialized or when a forwarded ref is not properly set up. The ref object exists but its current property is null because the component hasn't mounted yet or the ref wasn't passed correctly through forwardRef.

This ESLint warning appears when React components, especially those wrapped in forwardRef, memo, or higher-order components (HOCs), lack an explicit displayName property. While not breaking your app, missing displayNames make debugging harder in React DevTools and error stack traces.

This error occurs when using the recursive option with fs.mkdir() or fs.mkdirSync() in an older version of Node.js that does not support this feature. The recursive option was added in Node.js 10.12.0 to create directories recursively with a single command.

This error occurs when trying to use the useSearchParams hook in a Next.js Server Component. The hook is designed exclusively for Client Components to prevent stale values during partial rendering and maintain proper hydration.

This error occurs when Node.js fs.watch() reaches the system limit on file descriptors or inode watchers. The file watching subsystem cannot monitor additional files because the system has exhausted its available watching capacity.

This error occurs when using TypeScript's type-only import syntax in a JavaScript file or when file extensions don't match the content. The import type syntax, introduced in TypeScript 3.8, is only valid in .ts or .tsx files.

This TypeScript error occurs when using React.forwardRef without properly specifying generic type parameters for the ref and props types. TypeScript needs these type parameters to validate that refs are being passed correctly to the underlying component.

This error occurs when attempting to directly assign a value to ref.current in a forwardRef component when the ref is typed as a RefObject, which has an immutable current property. It commonly happens when mixing TypeScript types or trying to mutate refs passed from parent components.

This error occurs when trying to use getServerSideProps outside of page components in Next.js. The function must be exported from files in the /pages directory, not from regular components or when using the App Router.

This error occurs when trying to use React client hooks like useState, useEffect, or useRef in a Server Component. In Next.js 13+, all components are Server Components by default and must be explicitly marked as Client Components to use client-side hooks.

This error occurs when you try to import something from a module that doesn't export it. It's typically caused by mismatched import/export syntax, incorrect export names, or mixing default and named exports incorrectly.

This React hydration warning occurs when CSS-in-JS libraries inject style tags during server-side rendering that React does not expect during client-side hydration, causing a mismatch between server and client HTML.

This Next.js build error occurs when you try to cache dynamic route segments without proper revalidation configuration. The error indicates that routes with dynamic parameters like [slug] or [id] cannot use indefinite caching because their content is user-specific or request-dependent.

This error occurs when CommonJS module syntax (require/module.exports) is used in a browser environment without proper bundling or transpilation. Browsers natively support ES modules but do not recognize the CommonJS "exports" variable.

This error occurs when trying to pass a key prop to React's shorthand Fragment syntax (<>...</>). Only the explicit <Fragment> syntax supports the key attribute, which is needed when rendering lists of fragments.