Fixes
Next.js and React
Hydration errors, CORS failures, caching and upgrade problems in Next.js and React apps, each traced from the error message to a fix and a check.

659 fixes
Problems in this area
659 of 659 fixes
- tsconfig rejects allowImportingTsExtensions
error TS5023 pointing at allowImportingTsExtensions in tsconfig.json2 causes - AuthUserPoolException: Auth UserPool not configured in a Next.js app
AuthUserPoolException: Auth UserPool not configured.3 causes - Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'3 causes - Apollo Server rejects a request as a potential CSRF
This operation has been blocked as a potential Cross-Site Request Forgery (CSRF).3 causes - Apollo Client is blocked by CORS when the GraphQL server runs on AWS Lambda
Cross-Origin Request Blocked5 causes - A POST to a Google Apps Script web app returns 405 or a CORS error
Sorry, the file you have requested does not exist.3 causes - OpenAPI does not work in an ASP.NET Core minimal API
404 Not Found at /openapi/v1.json3 causes - Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call2 causes - React shows Attempted import error when importing a component or function
Attempted import error:2 causes - How to catch and handle a 422 from Axios in a Redux thunk
The validation messages are visible in the Network tab but not in the app4 causes - axios gets 429 Too Many Requests from a React app
Request failed with status code 4294 causes - Axios throws that the http adapter is not available inside a browser extension
Uncaught (in promise) Error: Error: Adapter 'http' is not available in the build2 causes - Axios request is not cancelled when a React component unmounts
The request still finishes and updates state after the component is gone or the id changed4 causes - AxiosError Network Error with code ERR_NETWORK in a React app
AxiosError {message: 'Network Error', name: 'AxiosError', code: 'ERR_NETWORK'}4 causes - Axios get works with a URL string but ignores the object passed as the second argument
The URL typed into the browser returns data, but axios.get(url, { id: 5 }) returns the unfiltered list3 causes - Can't resolve '../axios' in a React project
Module not found: Can't resolve '../axios' in 'F:\React\react-complete-guide\src\Component'3 causes - Axios returns 401 from a React app but the login works elsewhere
AxiosError: Request failed with status code 4013 causes - axios rejects with status code 404 in a React app
Uncaught (in promise) Error: Request failed with status code 4043 causes - An axios call never finishes when the API server stops answering
the request stays pending and the loading spinner never stops3 causes - Axios sends no cookie to an Express API even with withCredentials set to true
The request has no Cookie header although withCredentials is true4 causes - Entra ID access token has the Microsoft Graph audience instead of my API
aud: 00000003-0000-0000-c000-0000000000003 causes - Babel or Jest stops on JSX with an 'experimental syntax' error
SyntaxError: Support for the experimental syntax 'jsx' isn't currently enabled3 causes - Bootstrap 5 modal in React throws a 'backdrop' TypeError
Uncaught TypeError: Cannot read properties of undefined (reading 'backdrop')2 causes - Module not found: Can't resolve 'bootstrap/dist/css/bootstrap-theme.css'
Module not found: Can't resolve 'bootstrap/dist/css/bootstrap-theme.css'2 causes - Your build asks for node-sass and cannot load it
Error: Cannot find module 'node-sass'3 causes - TypeScript refuses JSX because the jsx option is not set
Cannot use JSX unless the '--jsx' flag is provided.2 causes - Module not found for react/jsx-runtime in a component library
Module not found: Error: Can't resolve 'react/jsx-runtime'2 causes - Chakra UI v3 does not work in my Vite and React project
Failed to resolve import "@/components/ui/provider" from "src/main.tsx". Does the file exist?4 causes - A Chrome extension content script cannot read another site's response
Cross-Origin Read Blocking (CORB) blocked cross-origin response https://api.example.com/price with MIME type application/json.3 causes - Chrome blocks a request from a public site to a local address
Look for and connect to any device on your local network4 causes - CKEditor 4 shows a 'this version is not secure' notification
This CKEditor 4.22.1 version is not secure. Consider upgrading to the latest one2 causes - Clerk cannot read its publishable key in a Next.js app
Clerk fails to get the publishable key from the environment variables3 causes - A web font served through CloudFront is blocked by CORS
Font from origin has been blocked from loading by Cross-Origin Resource Sharing policy4 causes - CodeIgniter 3 shows 'The action you have requested is not allowed.'
The action you have requested is not allowed.4 causes - TypeScript rejects a component that returns an array or other non-Element
'List' cannot be used as a JSX component.2 causes - The cors-anywhere.herokuapp.com demo proxy stopped working
A request to https://cors-anywhere.herokuapp.com/ returns an error or an opt-in message instead of the proxied page2 causes - Browser blocks a JSON request: Content-Type is not allowed by Access-Control-Allow-Headers
Request header field Content-Type is not allowed by Access-Control-Allow-Headers in preflight response.3 causes - Why you get a CORS error when the API is on your own domain
Reason: CORS header 'Access-Control-Allow-Origin' missing2 causes - The browser blocks your API response: no Access-Control-Allow-Origin header
Access to fetch at 'https://api.example.com/orders' from origin 'https://app.example.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.4 causes - The browser rejects the CORS preflight because the OPTIONS reply is not a 2xx
Response for preflight does not have HTTP ok status3 causes - A public website cannot reach your local dev server: local network request blocked
Access to fetch at 'http://localhost:3000/api' from origin 'https://app.example.com' has been blocked by CORS policy3 causes - CORS fails when you open an HTML file straight from disk
Reason: CORS request not HTTP3 causes - A Create React App build loads blank because the asset paths are wrong
Can't build create-react-app project with custom PUBLIC_URL3 causes - npm start runs, but the browser does not refresh when you save a file
Development server of create-react-app does not auto refresh4 causes - Create React App stops compiling because of an ESLint rule
npm start or npm run build stops with an ESLint problem listed by file and line4 causes - A .env variable is undefined in a Create React App project
process.env.REACT_APP_API_URL is undefined4 causes - The shell cannot find create-next-app
command not found: create-next-app2 causes - npx create-react-app prints a deprecation message or will not set up a new project
create-react-app is deprecated.2 causes - GENERATE_SOURCEMAP=false does nothing in a Create React App build on Windows
GENERATE_SOURCEMAP=false in a package.json script has no effect on a Windows machine4 causes - Cypress times out looking for an element by data-testid
Timed out retrying after 4000ms: Expected to find element: `[data-testid=login]`, but never found it.5 causes - Cypress refuses to start with 'Your configFile is invalid'
Your configFile is invalid: /path/to/cypress.config.ts5 causes - Google sign-in blocked with 403 disallowed_useragent inside an app
disallowed_useragent2 causes - django-cors-headers settings have no effect
Reason: CORS header 'Access-Control-Allow-Origin' missing4 causes - django-tailwind cannot find the npm executable (cPanel, Windows, Linux)
python manage.py tailwind install fails because npm or Node.js cannot be found3 causes - Electron app shows 404 or a blank window once it is packaged
The packaged app opens a blank window, the dev build works3 causes - Electron app blank with 'Refused to evaluate a string as JavaScript'
Uncaught EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive3 causes - esbuild's install script is blocked or fails when installing Vite with pnpm
ESBuild post-install failed when installing Vite3 causes - ESLint array-callback-return: expected to return a value in an arrow function
Expected to return a value at the end of arrow function3 causes - ESLint says an arrow function has an unneeded block body
Unexpected block statement surrounding arrow body; move the returned value immediately after the `=>`3 causes - ESLint fails with: Cannot find module 'next/babel'
Parsing error: Cannot find module 'next/babel'3 causes - ESLint cannot decide which copy of the @typescript-eslint plugin to use
ESLint couldn't determine the plugin "@typescript-eslint" uniquely.3 causes - ESLint cannot find the shared config named react-app
ESLint couldn't find the config "react-app" to extend from3 causes - ESLint cannot load a config called react
Failed to load config "react" to extend from.3 causes - ESLint cannot load the react plugin (eslint-plugin-react missing)
Failed to load plugin 'react' declared in '.eslintrc': Cannot find module 'eslint-plugin-react'2 causes - eslint --fix runs but the errors are still there
eslint --fix exits with code 1 and prints the same errors4 causes - ESLint no longer reads .eslintrc after upgrading to v9 or v10
ESLint runs after the upgrade but none of the rules from .eslintrc.json apply4 causes - ESLint says it cannot resolve a path to a module that does exist
Unable to resolve path to module 'react'. import/no-unresolved4 causes - ESLint says an element with role="button" must be focusable
Elements with the 'button' interactive role must be focusable4 causes - ESLint reports a let, const or function inside a switch case
Unexpected lexical declaration in case block.2 causes - ESLint reports no-unused-vars for React components and imports that are used
ESLint with React gives no-unused-vars errors3 causes - ESLint was configured to run using parserOptions.project, but the file is not in the TSConfig
Parsing error: ESLint was configured to run on `<tsconfigRootDir>/component/TestComponent.cy.ts` using `parserOptions.project`4 causes - ESLint parsing error: originalKeywordKind has been deprecated
Parsing error: DeprecationError: 'originalKeywordKind' has been deprecated since v5.0.0 and can no longer be used3 causes - ESLint cannot parse your JSX or modern syntax
Parsing error: Unexpected token <3 causes - ESLint cannot find the react-hooks/exhaustive-deps rule
Definition for rule 'react-hooks/exhaustive-deps' was not found2 causes - ESLint says an element in a list is missing its key prop
Missing "key" prop for element in iterator react/jsx-key3 causes - ESLint warns that the React version is not specified in eslint-plugin-react settings
Warning: React version not specified in eslint-plugin-react settings2 causes - Expo app never leaves the splash screen
App shows the splash screen forever and no error appears3 causes - Expo Go cannot load the app and shows Something went wrong
Something went wrong3 causes - tsconfig.json cannot find the file it extends in an Expo project
File 'expo-module-scripts/tsconfig.base' not found.2 causes - Your favicon works in the browser but not in Google Search results
Favicon appears in the browser tab but a default icon shows in Google Search4 causes - A React app cannot load an API response: blocked by ORB
net::ERR_BLOCKED_BY_ORB3 causes - response.json() fails after fetch with mode: no-cors
SyntaxError: Unexpected end of input4 causes - A fetch POST from React comes back as 415 Unsupported Media Type
415 Unsupported Media Type3 causes - fetch() resolves on 404 and 500, so catch never runs
catch never runs on a 404 or 500 response2 causes - findDOMNode warning in StrictMode, or findDOMNode missing in React 19
Warning: findDOMNode is deprecated in StrictMode3 causes - Attempted import error: firebase/app has no default export
Attempted import error: 'firebase/app' does not contain a default export (imported as 'firebase').3 causes - Firebase Auth says the API key is not valid
Firebase: Error (auth/api-key-not-valid.-please-pass-a-valid-api-key.)4 causes - Firebase sign-in fails with 'missing initial state' after a redirect
Unable to process request due to missing initial state.3 causes - Google sign-in popup blocked by Cross-Origin-Opener-Policy
Google sign-in with signInWithPopup cannot complete while the page is served with Cross-Origin-Opener-Policy: same-origin3 causes - SyntaxError in firebase-messaging-sw.js: import statement outside a module
Uncaught SyntaxError: Cannot use import statement outside a module (at firebase-messaging-sw.js:1:1)2 causes - Browser blocks a Firebase Storage request at the CORS preflight
Response to preflight request doesn't pass access control check: It does not have HTTP ok status3 causes - Firebase Messaging cannot register its default service worker
We are unable to register the default service worker.3 causes - Firefox blocks a cross-origin request even though the CORS headers are set
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource5 causes - Firestore addDoc throws on a field whose value is undefined
FirebaseError: Function addDoc() called with invalid data. Unsupported field value2 causes - FirebaseError: Expected first argument to collection() to be a CollectionReference
FirebaseError: Expected first argument to collection() to be a CollectionReference, a DocumentReference or FirebaseFirestore2 causes - Flask-WTF raises KeyError: A secret key is required to use CSRF
KeyError: 'A secret key is required to use CSRF.'4 causes - Flutter web warns that webOnlyWarmupEngine and webOnlySetPluginHandler are deprecated
The webOnlyWarmupEngine API is deprecated and will be removed in a future release.2 causes - Font Awesome icons vanish and the console shows CSP violations
Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self'".3 causes - Submitting a React form from code skips the onSubmit handler
formRef.current.submit() reloads the page or posts the form, but onSubmit is never called3 causes - Formik onSubmit never runs when the form is submitted
Clicking Submit does nothing and onSubmit is never called4 causes - Formik touched stays empty even after the user visits a field
touched is an empty object {}3 causes - The element vanishes at once instead of animating out
The element disappears instantly and the exit prop never runs4 causes - NativeViewGestureHandler must be used as a descendant of GestureHandlerRootView
Error: NativeViewGestureHandler must be used as a descendant of GestureHandlerRootView. Otherwise the gestures will not be recognized.3 causes - GitHub REST API returns 401 Unauthorized to a React fetch call
401 Unauthorized3 causes - Apollo Client query fails with Cannot query field on type Query
Cannot query field "xx" on type "Query"3 causes - There is no tailwind.config.js after installing Tailwind 4 and HeroUI in Next.js
tailwind.config.js not found in a new Next.js project3 causes - A video with the autoplay attribute does not start
Uncaught (in promise) NotAllowedError4 causes - html-webpack-plugin stops the build with 'Child compilation failed'
Error: Child compilation failed2 causes - react-i18next shows the wrong plural form for a count, or prints the key instead of the text
t('item', { count: 5 }) returns the singular text4 causes - Reading localStorage inside an iframe throws a SecurityError
Failed to read the 'localStorage' property from 'Window': Access is denied for this document.4 causes - A React component import fails because the file has no export with that name
Home does not contain an export named Home3 causes - Node.js stops with 'Invalid shorthand property initializer' on an object literal
SyntaxError: Invalid shorthand property initializer2 causes - ReferenceError: Cannot access __WEBPACK_DEFAULT_EXPORT__ before initialization
Uncaught ReferenceError: Cannot access '__WEBPACK_DEFAULT_EXPORT__' before initialization2 causes - Adding a property to an object fails with 'object is not extensible'
TypeError: Cannot add property x, object is not extensible3 causes - Jest fails when a component imports an .svg file
A test fails as soon as a component that imports an .svg file is loaded3 causes - Jest throws SyntaxError on import in a test or dependency
SyntaxError: Cannot use import statement outside a module3 causes - The shell says 'jest: command not found'
command not found: jest4 causes - Jest finds and runs the tests, but the coverage report is empty or incomplete
Coverage data for global was not found4 causes - jest-dom extend-expect import fails after upgrading to v6
Cannot find module '@testing-library/jest-dom/extend-expect' from 'jest.setup.js'2 causes - TypeScript cannot find toBeInTheDocument on expect()
Property 'toBeInTheDocument' does not exist on type 'Matchers<any>'4 causes - Jest tests crash on import() with a message about --experimental-vm-modules
TypeError: A dynamic import callback was invoked without --experimental-vm-modules3 causes - A modal test fails because the focus trap finds nothing to focus
Your focus-trap must have at least one container with at least one tabbable node in it at all times3 causes - A mocked axios call in Jest returns undefined or never resolves
TypeError: Cannot read properties of undefined (reading 'get')4 causes - Jest test fails with 'Cannot access ... before initialization' in jest.mock
ReferenceError: Cannot access 'mockSoundPlayer' before initialization3 causes - jest.mock() works at the top of the file but not inside a test
jest.mock('./api') inside it() has no effect; the real function runs3 causes - Jest finds no test files and exits with code 1
No tests found, exiting with code 15 causes - How to test a rejected promise in Jest without false passes
A test for an error case is green, but the function does not reject3 causes - Jest still skips my node_modules package after transformIgnorePatterns
A package under node_modules fails to parse in a Jest test (import or JSX syntax not converted)3 causes - Jest test throws Cannot redefine property: window
TypeError: Cannot redefine property: window3 causes - TypeScript says mockResolvedValue does not exist on an axios or fetch function
Property 'mockResolvedValue' does not exist on type '<T = any, R = AxiosResponse<T, any>, D = any>(url: string, config?: AxiosRequestConfig<D>) => Promise<R>'3 causes - Jest fails with SyntaxError: Unexpected token when testing a Next.js component
Jest encountered an unexpected token3 causes - Jest test fails with window is not defined
ReferenceError: window is not defined3 causes - Jest fails with window.matchMedia is not a function
TypeError: window.matchMedia is not a function2 causes - jQuery says it cannot use the in operator on a response from PHP
Uncaught TypeError: Cannot use 'in' operator to search for '324' in3 causes - SyntaxError: "undefined" is not valid JSON in a React app
SyntaxError: "undefined" is not valid JSON2 causes - SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data
SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data4 causes - jsPDF doc.html() saves nothing or a blank PDF in React
doc.html() runs but no PDF is downloaded3 causes - ESLint warns that img elements must have an alt prop in React
img elements must have an alt prop, either with meaningful text, or an empty string for decorative images4 causes - jwt-decode import fails in a React project
import jwt_decode from "jwt-decode" no longer works3 causes - Keycloak token issuer does not match when the app runs in Docker
Invalid token issuer3 causes - The browser refuses to show Keycloak inside a frame from my React app
violating Content Security Policy directive: frame-ancestors 'self'2 causes - Laravel cannot find a Sass or JS entry in the Vite manifest
Unable to locate file in Vite manifest: resources/sass/app.scss3 causes - Leaflet cannot find the map container element
Error: Map container not found.3 causes - Leaflet map loads but the marker icon is broken or missing
Marker shows as a broken image icon3 causes - Chrome says my localhost certificate is invalid
NET::ERR_CERT_AUTHORITY_INVALID4 causes - Failed to execute 'setItem' on 'Storage': quota exceeded, even after clear()
Failed to execute 'setItem' on 'Storage': Setting the value of 'state' exceeded the quota.3 causes - Lodash debounce fires on every keystroke in a React component
debounce fires on every keystroke in React4 causes - Chrome says it cannot use an icon from the web app manifest
Error while trying to use the following icon from the Manifest4 causes - Chrome reports a syntax error at line 1, column 1 for manifest.json
Manifest: Line: 1, column: 1, Syntax error.3 causes - Minified React error 130 in a production build
Minified React error #1302 causes - SyntaxError: Missing initializer in const declaration
SyntaxError: Missing initializer in const declaration2 causes - Module not found: Can't resolve '@babel/runtime/helpers/...'
Module not found: Can't resolve '@babel/runtime/helpers/objectWithoutPropertiesLoose'2 causes - Webpack cannot resolve popper.js for Bootstrap
Module not found: Error: Can't resolve 'popper.js'3 causes - Error acquiring a token in a React app that signs in with Azure
Token acquisition in iframe failed due to timeout.4 causes - MSW cannot register its worker because the script comes back as HTML
Failed to register a ServiceWorker for scope ('https://example.github.io/my-repo/') with script ('https://example.github.io/mockServiceWorker.js'): The script has an unsupported MIME type ('text/html').3 causes - MUI Autocomplete: getOptionLabel did not return a string
MUI: The `getOptionLabel` method of Autocomplete returned undefined instead of a string for3 causes - MUI Autocomplete warns that the value matches no option
MUI: The value provided to Autocomplete is invalid.3 causes - TypeScript rejects MUI Data Grid columns that set a type
A TypeScript error on the columns prop of DataGrid that points at a column's type property2 causes - The MUI X Data Grid ignores or rejects getRowId
getRowId is set but the grid still cannot find a row id3 causes - MUI X Data Grid squeezes its columns or does not scroll sideways
The grid renders with zero height or width4 causes - How to read the selected rows in an MUI X Data Grid
Nothing happens when rows are selected and onRowSelected is used3 causes - MUI X Data Grid shows the wrong page size or resets to page one
Data Grid shows all rows and has no pagination footer4 causes - MUI DataGrid warns that rows is an object when it expects an array
Warning: Failed prop type: Invalid prop `rows` of type `object` supplied to `ForwardRef(DataGrid)`, expected `array`.3 causes - MUI X Data Grid sorts in the wrong order or ignores a custom comparator
Column sorts but rows with empty cells jump to the top3 causes - The validation message never appears under an MUI X Date Picker
helperText is set on DatePicker but nothing renders under the field3 causes - Can't resolve AdapterDateFns in MUI X Date Pickers
Module not found: Can't resolve '@material-ui/lab/AdapterDateFns'3 causes - MUI date pickers cannot resolve date-fns/addDays
Module not found: Error: Can't resolve 'date-fns/addDays'2 causes - Module not found: Can't resolve an @mui/icons-material icon import
Module not found: Can't resolve '@mui/icons-material/FileDownload'3 causes - Module not found: Can't resolve '@material-ui/core' after an update or clone
Module not found: Can't resolve '@material-ui/core/Container'3 causes - MUI Select shows no label and no placeholder text
Select renders an empty box with no label3 causes - A Material UI Select without an initial value warns about an out-of-range value
MUI: You have provided an out-of-range value `undefined` for the select component.3 causes - MUI v5 crashes with Cannot read properties of undefined (reading 'create')
TypeError: Cannot read properties of undefined (reading 'create')3 causes - React cannot find the module @mui/x-data-grid
Module not found: Can't resolve '@mui/x-data-grid'3 causes - MUI X Date Picker ignores the default value or shows the wrong format
The picker is empty although a default value was passed3 causes - The renderInput prop stopped working on the MUI X DatePicker
renderInput does nothing on DatePicker, or TypeScript says the prop does not exist3 causes - React Navigation throws 'you have nested a NavigationContainer inside another'
Error: Looks like you have nested a 'NavigationContainer' inside another.2 causes - A build that passes locally fails on Netlify because of warnings
The build passes with npm run build on your machine and fails on Netlify2 causes - A React app on Netlify shows 404 when you reload a route
404 Not Found on Netlify when a route is reloaded3 causes - NextAuth sends the user to ?error=AccessDenied after Google sign in
AccessDenied2 causes - NextAuth CLIENT_FETCH_ERROR: the session call returned HTML
[next-auth][error][CLIENT_FETCH_ERROR]2 causes - NextAuth throws ERR_INVALID_URL only after deploy
TypeError [ERR_INVALID_URL]: Invalid URL3 causes - NextAuth logs NO_SECRET, or throws it in production
[next-auth][warn][NO_SECRET]2 causes - next-auth asks you to sign in with a different account
/api/auth/signin?error=OAuthAccountNotLinked4 causes - useSession throws because there is no SessionProvider above it
[next-auth]: `useSession` must be wrapped in a <SessionProvider />3 causes - npm run dev says next is not found in a fresh Next.js project
next: command not found2 causes - next-intl logs MISSING_MESSAGE and shows the key instead of text
MISSING_MESSAGE4 causes - next/link throws React.Children.only on its children
Error: React.Children.only expected to receive a single React element child.3 causes - Hydration failed after adding next-themes dark mode
Hydration failed error after wrapping the app in ThemeProvider3 causes - NextAuth credentials login answers 401 Unauthorized with error=CredentialsSignin
error=CredentialsSignin3 causes - TypeScript rejects the authorize function of the Credentials provider
TypeScript error on the authorize callback of the Credentials provider3 causes - A NextAuth credentials login sends the browser back to /api/auth/signin?csrf=true
http://localhost:3000/api/auth/signin?csrf=true3 causes - getSession finds no user inside a Next.js API route
getSession() returns null inside pages/api even though the user is signed in3 causes - getToken({ req }) gives null even though the user is signed in
I can't get token with getToken({req})3 causes - The user is undefined inside the NextAuth session callback
user is undefined in the session callback3 causes - The NextAuth session shows old data until the page is refreshed
Next-auth session doesn't update until I refresh the page or navigate to another page4 causes - NextAuth shows 'There is a problem with the server configuration'
There is a problem with the server configuration.5 causes - Upgrading to Next.js 16: middleware becomes proxy, and the other things that break
The "middleware" file convention is deprecated6 causes - A Next.js API endpoint returns 404 Not Found
404 Not Found3 causes - A Next.js route handler is cut off after a fixed time
Route handler stops after a fixed number of seconds on production but not locally3 causes - fetch('/api/...') returns 404 for a route handler in the app folder
404 Not Found when calling an /api URL that has a route.ts4 causes - A Next.js component is marked async but it runs as a Client Component
async/await is not yet supported in Client Components4 causes - next build stops because of TypeScript errors
How to disable typescript for failing my builds with nextjs?2 causes - next build stops because of ESLint errors, and next lint is gone
Need to disable some ESLint rules3 causes - TypeScript cannot resolve import './globals.css' in Next.js
Cannot find module or type declarations for side-effect import of './globals.css'.2 causes - Next.js fails with Cannot find module 'tailwindcss'
Error: Cannot find module 'tailwindcss'3 causes - ChunkLoadError: Loading chunk failed after a Next.js deploy
ChunkLoadError: Loading chunk2 causes - Next.js shows Application error: a client-side exception has occurred
Application error: a client-side exception has occurred (see the browser console for more information).4 causes - Next.js warns about invalid options in next.config
A warning that next.config.js has invalid options and names an unexpected property3 causes - Setting or deleting a cookie in Next.js throws instead of saving it
Error: Cookies can only be modified in a Server Action or Route Handler3 causes - A browser blocks a request to a Next.js API route with a CORS error
Access to fetch at 'https://api.example.com/api/items' from origin 'https://app.example.com' has been blocked by CORS policy4 causes - next dev is very slow to compile and refresh
The first visit to every route takes many seconds in development4 causes - next dev starts but the page hangs on compiling for minutes
npm run dev starts, but the browser tab loads for minutes6 causes - Next.js build logs 'Dynamic server usage' for a route handler that reads searchParams
Dynamic server usage: Page couldn't be rendered statically because it used `nextUrl.searchParams`3 causes - A Next.js environment variable is undefined in the browser or after deploy
process.env.API_URL is undefined4 causes - ESLint 9 ignores or breaks the Next.js lint config
ESLint 9 is not working properly with Next 154 causes - Next.js: Event handlers cannot be passed to Client Component props
Event handlers cannot be passed to Client Component props.3 causes - next build fails while prerendering pages
Export encountered errors on following paths3 causes - Warning: Extra attributes from the server in the console
Warning: Extra attributes from the server: data-new-gr-c-s-check-loaded,data-gr-ext-installed3 causes - Next.js cannot load its SWC compiler binary
Failed to load SWC binary4 causes - The favicon does not show up in a Next.js app
No favicon in the browser tab4 causes - Cookies are missing on a fetch request in a Next.js app
fetch with credentials: 'include' sends no Cookie header4 causes - TypeError: fetch failed in a Next.js Server Component or route handler
TypeError: fetch failed3 causes - Next.js shows old data even though fetch uses cache: 'no-store'
fetch(url, { cache: 'no-store' }) returns the same data after the source changed4 causes - document.getElementById returns null in a Next.js component although the id is in the JSX
document.getElementById('my-id') returns null3 causes - getServerSideProps never runs, or its data never reaches the component
getServerSideProps is defined, but the component never receives its data3 causes - getStaticProps is ignored or rejected in a Next.js project
"getStaticProps" is not a valid Next.js entry export value4 causes - Error serializing props returned from getStaticProps
Error serializing `.post.publishedAt` returned from `getStaticProps` in "/blog/[slug]".3 causes - Next.js stops the build because a component imports a global stylesheet
Global CSS cannot be imported from files other than your Custom <App>3 causes - A Google Font does not show in the Next.js App Router
How to import custom google fonts in NextJS 13? Link tags not working4 causes - React hydration failed: the server HTML and the first browser render differ
Hydration failed because the server rendered HTML didn't match the client. As a result this tree will be regenerated on the client.5 causes - next/image returns 400 Bad Request from /_next/image
400 Bad Request4 causes - next build fails because next/image uses the default loader in a static export
Build fails when output: 'export' is set and next/image is imported3 causes - next/image shows nothing for an image from another domain
400 Bad Request on /_next/image?url=https%3A%2F%2F...3 causes - next/image ignores layout, objectFit and layout="fill"
Next.JS Image `layout='fill'` is broken3 causes - next/image fails with The requested resource isn't a valid image
The requested resource isn't a valid image for /public/logo.png received text/html; charset=utf-82 causes - next/image pictures show up late or load slowly
The hero image appears after the rest of the page4 causes - Next.js warns that images.domains is deprecated
The "images.domains" configuration is deprecated. Please use "images.remotePatterns" configuration instead.4 causes - Importing an SVG file in Next.js fails or shows nothing
Can't import SVG into Next.js3 causes - Next.js warns that next.config.js is invalid
warning Invalid next.config.js3 causes - "invariant expected app router to be mounted" in a Next.js app
Uncaught Error: invariant expected app router to be mounted3 causes - A Next.js Link wrapped in a button behaves strangely
unexpected behavior of Next/Link when it is a child of a button2 causes - The page keeps its scroll position after a Next.js Link navigation
Link navigates but the new page opens scrolled down3 causes - A custom font file added with next/font/local does not load or cannot be found
The build cannot find the font file given in src3 causes - Next.js middleware breaks when it imports Node.js crypto
Middleware or a package it imports fails to build because the Edge runtime does not support the Node.js crypto module4 causes - Next.js middleware (proxy) does not run for my routes
console.log inside middleware never prints3 causes - The browser gives up after Next.js middleware redirects the same page again and again
ERR_TOO_MANY_REDIRECTS4 causes - Next.js middleware throws 'URL is malformed. Please use only absolute URLs'
Error: URL is malformed "/login". Please use only absolute URLs - https://nextjs.org/docs/messages/middleware-relative-urls3 causes - Next.js build fails on a Node.js module like net or node:buffer in browser code
Module not found: Can't resolve 'net'2 causes - Next.js says Module parse failed: you may need an appropriate loader
Module parse failed: Unexpected token3 causes - next export is gone: moving to output: 'export'
The "next export" command has been removed in favor of "output: export" in next.config.js3 causes - Next.js throws NEXT_REDIRECT and the redirect never happens
NEXT_REDIRECT2 causes - ESLint warns 'Do not use <img>' in a Next.js project
Do not use <img>. Use Image from 'next/image' instead.3 causes - The custom Next.js 404 page does not show for unknown URLs
Not-found page does not work in Next.js 135 causes - The Open Graph image of a Next.js page does not appear when shared
og:image is missing from the page source4 causes - Next.js: only plain objects can be passed to Client Components
Only plain objects, and a few built-ins, can be passed to Client Components from Server Components. Classes or null prototypes are not supported.3 causes - next build with output: 'export' fails on a dynamic route
missing "generateStaticParams()" with output: export3 causes - A dynamic route like /posts/[id] returns 404 in the Next.js Pages Router
404 | This page could not be found4 causes - Type error after upgrading: params does not satisfy the PageProps constraint
Type '{ params: { id: string; }; }' does not satisfy the constraint 'PageProps'4 causes - A local image in a Next.js project returns 404 or will not render
GET /public/images/logo.png 404 (Not Found)3 causes - Using a context provider or hook in a Next.js Server Component fails
Error: React Context is unavailable in Server Components3 causes - A Leaflet map crashes the Next.js build or shows up broken
ReferenceError: window is not defined3 causes - Next.js stops with 'document is not defined' while it renders on the server
ReferenceError: document is not defined3 causes - Next.js refuses to run on an old Node.js version
Next.js App Requires Node.js Version >= v18.17.0, but Encountering Error with Node.js 16.20.23 causes - res.status is not a function in a Next.js API endpoint
TypeError: res.status is not a function2 causes - router.push() does nothing or throws in a Next.js app
Error: NextRouter was not mounted3 causes - router.query is empty or undefined the first time a page renders
router.query is {} on the first render and filled in on the next one4 causes - A script you added to a Next.js page never runs
The script tag is in the page source but the code never runs4 causes - A Next.js Server Action cannot read the values the user submitted
formData.get('email') returns null although the field was filled in4 causes - A custom error from the server arrives at the client as a generic message
error.message is a generic text in production but the real message in development3 causes - styled-components styles flash or mismatch after server render in Next.js
Warning: Prop `className` did not match. Server: "..." Client: "..."3 causes - Supabase sign in redirects to localhost or an internal address in production
Redirected to http://localhost:3000 after Google sign in on the live site2 causes - React says a Suspense boundary was updated before it finished hydrating
This Suspense boundary received an update before it finished hydrating.3 causes - Tailwind classes have no effect in a Next.js app
Tailwind classes are in the markup but nothing is styled5 causes - Importing useActionState from react fails in a Next.js project
import { useActionState } from 'react' fails after following the Next.js forms tutorial4 causes - useState fails in a child component in the Next.js App Router
You're importing a component that needs useState. This React Hook only works in a Client Component.3 causes - My Next.js app deployed to Vercel shows a 404 page not found
404: NOT_FOUND4 causes - Module not found on Vercel but the build passes on my machine
Module not found: Can't resolve3 causes - FATAL ERROR: heap out of memory during a webpack or npm build
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory3 causes - Node.js fails with uv_cwd ENOENT when its folder is gone
Error: ENOENT: no such file or directory, uv_cwd2 causes - npm ci fails because package.json and the lockfile disagree
npm error code EUSAGE3 causes - npm refuses to install @material-ui/core 4 next to a newer React
npm error code ERESOLVE3 causes - npm cannot resolve the dependency tree when installing MUI icons
npm error code ERESOLVE3 causes - npm cannot resolve @testing-library packages and their peer dependencies
when using create-react-app dependencies @testing-library could not resolve3 causes - npm refuses to install a React library because of peerDependencies
The package react@15.3.2 does not satisfy its siblings' peerDependencies requirements2 causes - npm install stops with a response timeout while fetching a package
Response timeout while trying to fetch https://registry.npmjs.org/react-is (over 30000ms)4 causes - PowerShell blocks npx because running scripts is disabled
npx : File C:\Program Files\nodejs\npx.ps1 cannot be loaded because running scripts is disabled on this system.3 causes - Nuxt shows edits only after a manual browser refresh
Save a file and the browser stays the same until F53 causes - Nuxt images with a dynamic :src show broken or 404
Dynamic image works with a fixed path but breaks when :src uses a variable2 causes - nvm for Windows installs but npm cannot be found
Cannot find the npm file4 causes - Your project has a package.json but no node_modules folder
node_modules does not exist after cloning the project3 causes - pdf.js warns 'Setting up fake worker' when a PDF opens in a React app
Warning: Setting up fake worker.4 causes - A Vue component does not re-render when the Pinia store changes
The store value changes in Vue devtools but the template still shows the old value3 causes - Playwright opens a small window instead of a full-size one
Playwright window won't launch full screen3 causes - Playwright says the execution context was destroyed because of a navigation
page.evaluate: Execution context was destroyed, most likely because of a navigation.4 causes - Playwright cannot open a headed browser on a Linux server or in Docker
Playwright will be unable to locate browser executables3 causes - The shell says pnpm: command not found
pnpm: command not found3 causes - window.postMessage between a React page and an iframe does nothing
postMessage runs without an error but the other window never logs anything3 causes - Prettier does nothing when you format a .tsx file in VS Code
Format Document does nothing on a .tsx file4 causes - npx prisma db seed stops with 'Command failed with exit code 1'
Error: Command failed with exit code 1: ts-node --compiler-options {"module":"CommonJS"} prisma/seed.ts3 causes - TypeScript cannot find a new Prisma model on the client
Property 'post' does not exist on type 'PrismaClient'3 causes - Prisma works locally but fails on Vercel with a stale client or a missing prisma command
PrismaClientInitializationError3 causes - React Router throws that a custom component is not a <Route>
Error: [PrivateRoute] is not a <Route> component. All component children of <Routes> must be a <Route> or <React.Fragment>3 causes - Quasar or webpack build fails on ajv/dist/compile/codegen
Error: Cannot find module 'ajv/dist/compile/codegen'2 causes - Rails rejects a POST with 'Can't verify CSRF token authenticity'
WARNING: Can't verify CSRF token authenticity4 causes - Parse error: adjacent JSX elements must be wrapped in an enclosing tag
Parse Error: Adjacent JSX elements must be wrapped in an enclosing tag3 causes - The onClick handler on a React <a> tag never runs, or the page jumps away
The handler runs when the page renders, and nothing happens when the link is clicked4 causes - The browser still autofills a React input marked autoComplete off
<input autoComplete="off" /> still shows saved suggestions or a filled password3 causes - SyntaxError: await is only valid in async functions, in a React or Redux file
SyntaxError: await is only valid in async functions, async generators and modules2 causes - TypeScript 7031 on a destructured children prop in React
Binding element 'children' implicitly has an 'any' type.ts(7031)2 causes - React-Bootstrap Navbar links reload the page or do not route
Clicking a Navbar link reloads the whole page3 causes - A React component crashes while destructuring props or state
TypeError: Cannot destructure property 'name' of 'undefined' as it is undefined.3 causes - Cannot find module react/jsx-runtime in a React build
Cannot find module 'react/jsx-runtime'3 causes - React warns it cannot flush updates because it is already rendering
Warning: flushSync was called from inside a lifecycle method. React cannot flush when React is already rendering. Consider moving this call to a scheduler task or micro task.3 causes - TypeError: Cannot read properties of null (reading 'useContext') in React
TypeError: Cannot read properties of null (reading 'useContext')4 causes - A React component calls includes or slice on a value that is still undefined
TypeError: Cannot read properties of undefined (reading 'includes')2 causes - A React component crashes calling .map on undefined
TypeError: Cannot read properties of undefined (reading 'map')3 causes - Click handler in a React class component throws on this.setState
TypeError: Cannot read properties of undefined (reading 'setState')2 causes - React warns about updating one component while another renders
Warning: Cannot update a component (`Parent`) while rendering a different component (`Child`)4 causes - A React checkbox that ignores clicks or never changes state
You provided a `checked` prop to a form field without an `onChange` handler. This will render a read-only field.4 causes - A child component keeps showing old data after its prop changed
The parent state changes in the console but the child still shows the first value3 causes - React logs 'Consider adding an error boundary to your tree' and the page goes blank
Consider adding an error boundary to your tree to customize error handling behavior.3 causes - My React countdown timer sticks, skips seconds or counts too fast
The timer goes from 60 to 59 and stops3 causes - defaultProps stopped working on a function component in React 19
A prop is undefined after upgrading to React 19 although Component.defaultProps sets it2 causes - The React dev server cannot proxy a request to the backend (ECONNREFUSED)
Could not proxy request /pusher/auth from localhost:3000 to http://localhost:50003 causes - The React Components and Profiler tabs do not show in Chrome DevTools
The Components and Profiler tabs are missing from Chrome DevTools4 causes - ESLint react/display-name warning on a React component
Component definition is missing display name react/display-name3 causes - React warns that a div is nested inside a p tag
<div> cannot appear as a descendant of <p>3 causes - Warning: React does not recognize a prop on a DOM element
Warning: React does not recognize the `isActive` prop on a DOM element.3 causes - createRoot from react-dom/client cannot be imported after upgrading to React 18
TypeScript cannot find the module react-dom/client3 causes - React warns that each child in a list should have a unique key prop
Warning: Each child in a list should have a unique "key" prop.4 causes - React was asked to render something that is not a component (it got undefined)
Error: Element type is invalid: expected a string (for built-in components) or a class/function (for composite components) but got: undefined.4 causes - An error boundary in React that never shows its fallback
The whole screen goes blank when a component throws2 causes - Webpack warns that React was not found in the react package
export 'React' (imported as 'React') was not found in 'react'2 causes - React throws when a file input is given a value
Failed to set the 'value' property on 'HTMLInputElement'2 causes - ESLint warns that a React file exports more than components
Fast refresh only works when a file only exports components. Use a new file to share constants or functions between components.4 causes - fireEvent.click runs but nothing changes in the test
Unable to find an element with the text: Clicked3 causes - TypeScript: 'ref' does not exist on IntrinsicAttributes for my component
Property 'ref' does not exist on type 'IntrinsicAttributes'3 causes - A ref on your own component never reaches the input
Function components cannot be given refs. Attempts to access this ref will fail.3 causes - react-hook-form does not focus a Controller field after a failed submit
Validation errors show but the cursor does not jump to the first invalid field3 causes - A disabled input is missing from react-hook-form's submitted data
disabled input value is undefined in handleSubmit2 causes - React Hook Form: the submit button does nothing and onSubmit never runs
Clicking submit does nothing and onSubmit is never logged4 causes - React Hook Form isDirty does not go back to false
formState.isDirty is still true after the user types the original value back4 causes - react-hook-form: an optional number input gives NaN instead of a number or null
The field value is NaN instead of a number3 causes - react-hook-form custom errors disappear, or never clear, after setError
setError message flashes and then disappears on submit3 causes - setValue does nothing for a field inside a Material UI dialog
setValue is called but the input in the dialog stays empty3 causes - react-hook-form shows no error when you leave a field
No error message appears after tabbing out of an invalid field3 causes - ESLint says a React Hook is called conditionally, in useCallback or any other hook
React Hook "useCallback" is called conditionally. React Hooks must be called in the exact same order in every component render.4 causes - The exhaustive-deps warning on useEffect, and how to clear it properly
React Hook useEffect has a missing dependency: 'roomId'. Either include it or remove the dependency array4 causes - React Hook "useState" cannot be called at the top level, or in a function that is not a component
React Hook "useState" cannot be called at the top level. React Hooks must be called in a React function component or a custom React Hook function3 causes - React dev server in Docker does not reload when you save a file
Page does not refresh after saving a file in the editor3 causes - react-icons import fails: module not found or icon not exported
Module not found: Error: Can't resolve 'react-icons/fa'3 causes - Local images do not show up in a React app built with Vite
Broken image icon where <img src="./logo.png"> should show4 causes - A React input keeps its old text when defaultValue changes
Input shows the first record's value after selecting another record3 causes - React warns about null values and controlled or uncontrolled inputs
A component is changing an uncontrolled input to be controlled3 causes - React error: input is a void element tag and must neither have children
input is a void element tag and must neither have `children` nor use `dangerouslySetInnerHTML`3 causes - React: TypeError, invalid attempt to destructure non-iterable instance
TypeError: Invalid attempt to destructure non-iterable instance3 causes - React says a Hook was called where React is not rendering a component
Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:4 causes - ESLint says an anchor needs a valid, navigable href in React
The href attribute requires a valid address. Provide a valid, navigable address as the href value.3 causes - ESLint react/no-array-index-key: Do not use Array index in keys
Do not use Array index in keys3 causes - ESLint says a JSX component is not defined (react/jsx-no-undef)
'Hello' is not defined react/jsx-no-undef3 causes - React.lazy or next/dynamic resolves to undefined
Element type is invalid. Received a promise that resolves to: undefined. Lazy element type must resolve to a class or function.3 causes - react-leaflet build fails with Module parse failed
Failed to compile ./node_modules/@react-leaflet/core/esm/path.js2 causes - ReferenceError: localStorage is not defined during server rendering
ReferenceError: localStorage is not defined3 causes - React: Maximum update depth exceeded or Too many re-renders
Too many re-renders. React limits the number of renders to prevent an infinite loop.3 causes - Minified React error #200 in a production build
Uncaught Error: Minified React error #2003 causes - ESLint react/prop-types reports a prop as missing in props validation
'name' is missing in props validation3 causes - react-modal warns that the app element is not defined
Warning: react-modal: App element is not defined. Please use `Modal.setAppElement(el)` or set `appElement={el}`3 causes - Build fails because react-moment cannot find the moment package
Module not found: Can't resolve 'moment'4 causes - React Native says the application has not been registered
Application has not been registered3 causes - TypeScript marks className as an error on React Native components
Property 'className' does not exist on type3 causes - Jest fails to parse a React Native or Expo dependency
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax3 causes - TextInput warns that value is a number but a string is expected
Warning: Failed prop type: Invalid prop `value` of type `number` supplied to `TextInput`, expected `string`2 causes - yarn is not recognized when running a React Native project
'yarn' is not recognized as an internal or external command, operable program or batch file.3 causes - ESLint react/no-unescaped-entities on an apostrophe or quote in JSX
react/no-unescaped-entities3 causes - React throws 'Objects are not valid as a React child'
Objects are not valid as a React child (found: object with keys {id, name})3 causes - offsetX and offsetY are missing on a React mouse event
event.offsetX is undefined2 causes - A key press does nothing on a div with onKeyDown in React
onKeyDown on a div never runs, no console output4 causes - Parsing error: Identifier 'React' has already been declared
Parsing error: Identifier 'React' has already been declared2 causes - @react-pdf/renderer fails to install or run after a React or Next.js upgrade
TypeError: ba.Component is not a constructor3 causes - A PropTypes warning says a required prop is undefined
Warning: Failed prop type: The prop `onSave` is marked as required in `Editor`, but its value is `undefined`.3 causes - TanStack Query says the query function returned undefined
Query data cannot be undefined. Please make sure to return a value other than undefined from your query function2 causes - A file download with React Query fails when you call createObjectURL
TypeError when calling URL.createObjectURL with the data from useQuery or useMutation4 causes - invalidateQueries or refetch does nothing in React Query and React Native
invalidateQueries does not refetch4 causes - TanStack Query throws 'No QueryClient set' on useQuery
Error: No QueryClient set, use QueryClientProvider to set one2 causes - onSuccess and onError on useQuery do nothing after upgrading TanStack Query
onSuccess is not called in useQuery2 causes - TanStack Query useInfiniteQuery reloads every page again and again
the list flashes and reloads when you switch back to the browser tab3 causes - useQuery returns data as undefined
const { data } = useQuery(...) logs undefined3 causes - A React range slider that will not move or does not update its value
You provided a `value` prop to a form field without an `onChange` handler. This will render a read-only field. If the field should be mutable use `defaultValue`. Otherwise, set either `onChange` or `readOnly`.4 causes - Cannot read properties of null: ReactCurrentDispatcher or useState
TypeError: Cannot read properties of undefined (reading 'ReactCurrentDispatcher')3 causes - useDispatch or useSelector throws: could not find react-redux context value
Error: could not find react-redux context value; please ensure the component is wrapped in a <Provider>4 causes - $RefreshSig$ or $RefreshReg$ is not defined with React Refresh in webpack
$RefreshSig$ is not defined2 causes - React says a component rendered fewer hooks than the last render
Uncaught Error: Rendered fewer hooks than expected. This may be caused by an accidental early return statement.2 causes - React warns that rendering a Context directly is not supported
Rendering <Context> directly is not supported and will be removed in a future major release2 causes - React Router throws: A Route is only ever to be used as the child of Routes
Error: A <Route> is only ever to be used as the child of <Routes> element, never rendered directly. Please wrap your <Route> in a <Routes>.3 causes - Show a 404 page for unknown URLs in React Router
Blank page on a URL that no route matches2 causes - A query string parameter will not go away with useSearchParams
The param is still in the URL after searchParams.delete()3 causes - React throws 'You cannot render a <Router> inside another <Router>'
You cannot render a <Router> inside another <Router>.3 causes - Link cannot be imported from react-router
export 'Link' (imported as 'Link') was not found in 'react-router'3 causes - A React Router route error shows the default error page instead of my boundary
The default error screen appears instead of my own error component3 causes - React Router routes return 404 or a blank page on GitHub Pages
404 on refresh at a path such as /about2 causes - TypeScript: history.push does not exist after upgrading React Router
Property 'push' does not exist on type 'History'2 causes - Clicking a React Router Link changes the URL but the new page stays blank
The URL changes to /dashboard/settings but the page still shows the old content3 causes - A React Router Link fails because useContext returns null
TypeError: t.useContext(...) is null4 causes - React Router shows a blank page and warns about a leaf route
Matched leaf route at location "/" does not have an element or Component. This means it will render an <Outlet /> with a null value by default resulting in an "empty" page.3 causes - Child routes in React Router do not render inside the parent page
The parent layout renders but the child page is empty3 causes - React Router shows a blank page or the error screen for URLs that match no route
A mistyped URL shows a blank page or a default error screen2 causes - Calling redirect() in a React Router component does nothing
The URL stays the same after calling redirect('/login')3 causes - TypeScript says your Router is missing location and navigator
Type '{ children: Element[]; }' is missing the following properties from type 'RouterProps': location, navigator2 causes - A React Router route returns 403 or 404 from S3 when you refresh
403 Forbidden when refreshing /dashboard on the S3 website URL3 causes - Navigating between two React Router paths that use one component does not reset it
The URL changes but the form, scroll or counter keeps the old values3 causes - Switch, Redirect or useHistory missing after a React Router upgrade
Attempted import error: 'Switch' is not exported from 'react-router-dom'3 causes - props.history is undefined after upgrading React Router
TypeError: Cannot read properties of undefined (reading 'push')3 causes - Warn users before they leave a React Router page with unsaved changes
Prompt or usePrompt stops working after upgrading from React Router v53 causes - useRoutes() fails because no Router wraps the component
Error: useRoutes() may be used only in the context of a <Router> component.2 causes - A global from a script tag in index.html is 'not defined' in React
'Widget' is not defined no-undef2 causes - A script tag inside dangerouslySetInnerHTML never executes
The script tag is visible in DevTools Elements but its code never runs3 causes - npm start fails because react-scripts is not found
sh: react-scripts: command not found3 causes - React warns about selected on an option element
Use the `defaultValue` or `value` props on <select> instead of setting `selected` on <option>.3 causes - setState runs while React is rendering a class component
Warning: setState(...): Cannot update during an existing state transition (such as within `render`).3 causes - React state still shows the old value right after setState
console.log(count) prints the old value right after setCount(count + 1)2 causes - setTimeout in a React component fires at the wrong time or never
The callback runs immediately instead of after the delay5 causes - react-slick builds, but the slick-carousel CSS import cannot be found
Module not found3 causes - A React timer, interval or handler keeps using an old state value
A setTimeout alert shows the value from before the click3 causes - createRoot fails with Target container is not a DOM element
Error: Target container is not a DOM element.3 causes - fireEvent in React Testing Library does not change the input value
expect(input).toHaveValue('new') fails: received the old value3 causes - Tests print that ReactDOM.render is no longer supported in React 18
Warning: ReactDOM.render is no longer supported in React 18. Use createRoot instead. Until you switch to the new API, your app will behave as if it's running React 17.3 causes - Testing a custom hook fails after upgrading to React 18
renderHook from @testing-library/react-hooks fails with React 183 causes - React Testing Library cannot find an element by its data-testid
Unable to find the element with data-testid4 causes - Testing Library: Unable to find an element with the text /learn react/i in a new React app test
TestingLibraryElementError: Unable to find an element with the text: /learn react/i3 causes - A React test warns that a state update was not wrapped in act()
Warning: An update to <Component> inside a test was not wrapped in act(...)4 causes - waitFor passes too early, never retries or times out in a React test
Unable to find an element4 causes - react-toastify: toast() runs but nothing shows, or it looks broken
toast() is called, no toast appears on screen4 causes - React stops with 'Too many re-renders' as soon as a component loads
Too many re-renders. React limits the number of renders to prevent an infinite loop.2 causes - TypeScript says void is not assignable to ReactNode in a React component
Error: Type 'void' is not assignable to type 'ReactNode'2 causes - TypeScript rejects an onClick handler because the type is void
Type 'void' is not assignable to type '((event: MouseEvent<HTMLInputElement>) => void) | undefined'2 causes - React says .map is not a function on your data
TypeError: results.map is not a function4 causes - TypeScript rejects the content you put between a React component's tags
Property 'children' does not exist on type 'IntrinsicAttributes & Props'3 causes - The form still reloads the page in React with TypeScript
The page refreshes and the form fields clear when you press the submit button4 causes - React warns that an input switched from uncontrolled to controlled
Warning: A component is changing an uncontrolled input to be controlled.3 causes - TypeError: Cannot destructure property of useContext(...) as it is undefined
TypeError: Cannot destructure property 'user' of '(0 , react__WEBPACK_IMPORTED_MODULE_0__.useContext)(...)' as it is undefined.2 causes - React warns when you pass an async function to useEffect
It looks like you wrote useEffect(async () => ...) or returned a Promise.3 causes - A React component keeps listeners or fetches alive after it leaves
Handlers keep firing after the component is gone3 causes - Using useId to make list keys in React
List rows lose their state or typed text when the list updates3 causes - useNavigate and Link throw because no router is above them
Uncaught Error: useNavigate() may be used only in the context of a <Router> component.2 causes - React Router throws because useNavigation has no data router above it
useNavigation must be used within a data router.3 causes - ref.current is null when you read a useRef in React
TypeError: Cannot read properties of null (reading 'focus')3 causes - ref.current may be null or undefined with useRef in React and TypeScript
TypeScript reports that ref.current may be null3 causes - TypeScript rejects a useRef ref passed to an input element
Type 'MutableRefObject<HTMLInputElement | undefined>' is not assignable to type 'LegacyRef<HTMLInputElement> | undefined'2 causes - useSelector keeps re-rendering a component although the data did not change
A component re-renders after every dispatched action, even unrelated ones4 causes - useState keeps the old value after the prop changes
A form or card still shows the previous item after the parent passes a new prop3 causes - useState(null) then setting an object fails in TypeScript
'user' is possibly 'null'.3 causes - TypeScript rejects a value passed to a useState setter
Type 'number' is not assignable to type 'SetStateAction<undefined>'.2 causes - A library fails to build because react has no useSyncExternalStore
export 'useSyncExternalStore' (imported as 'React') was not found in 'react'2 causes - React warns that an <a> is nested inside another <a>
Warning: validateDOMNesting(...): <a> cannot appear as a descendant of <a>.2 causes - React warns that a div sits directly inside a tbody
Warning: validateDOMNesting(...): <div> cannot appear as a child of <tbody>.2 causes - React warns that text cannot appear as a child of a table row
In HTML, text nodes cannot be a child of <tr>. This will cause a hydration error.3 causes - React warning: <th> cannot appear as a child of <thead>
Warning: validateDOMNesting(...): <th> cannot appear as a child of <thead>.3 causes - React warns that a form field has a value but no onChange handler
You provided a `value` prop to a form field without an `onChange` handler. This will render a read-only field. If the field should be mutable use `defaultValue`. Otherwise, set either `onChange` or `readOnly`.5 causes - Editing a component reloads the page instead of hot-updating it
Editing a component triggers a full page reload3 causes - The built React app is blank, though it works in development
Blank white page after npm run build3 causes - Yup string().matches() rejects values that should pass
An optional phone or zip field shows the pattern error when left empty3 causes - createStore is struck through and marked @deprecated in Redux
createStore shown with a strikethrough and marked @deprecated in the editor2 causes - Module not found: can't resolve 'redux' or 'react-redux'
Module not found: Error: Can't resolve 'redux'3 causes - Redux store throws 'does not have a valid reducer'
Store does not have a valid reducer. Make sure the argument passed to combineReducers is an object whose values are reducers.3 causes - Redux Toolkit warns that a non-serializable value is in an action or state
A non-serializable value was detected in an action, in the path: `payload.dueDate`3 causes - The browser refuses to set a header such as User-Agent or Cookie
Refused to set unsafe header "User-Agent"4 causes - waitForNextUpdate of renderHook times out or is missing
waitForNextUpdate times out in a renderHook test3 causes - ESLint reports an invalid type in a template literal in TypeScript
Invalid type "any" of template literal expression3 causes - An RTK Query request is blocked by CORS in the browser
The browser console reports that the request was blocked by the CORS policy3 causes - RTK Query refetch on a button click shows the same data
Clicking the button runs the handler but no request appears in the Network tab4 causes - RTK Query keeps repeating a request that fails
The same failed request appears about six times in the network tab4 causes - getBy query fails in React Testing Library because several elements match
TestingLibraryElementError: Found multiple elements4 causes - Dart Sass warns that the legacy JS API will be removed
The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0.2 causes - Sass says a mixin is undefined although the file defines it
SassError: Undefined mixin.4 causes - Sentry says Invalid token (401) during the Next.js build
Sentry reported an error: Invalid token (http status: 401)3 causes - Sentry: Non-Error promise rejection captured with value in a React app
Non-Error promise rejection captured with value: Object Not Found Matching Id3 causes - firebase-messaging-sw.js throws a DOMException on importScripts
A DOMException from importScripts in the service worker (NetworkError, SyntaxError or TypeError)3 causes - Service worker registration fails because the script comes back as HTML
Service Worker registration error: Unsupported MIME type ('text/html')2 causes - npm install fails with 'sh: node-gyp-build: command not found'
sh: node-gyp-build: command not found2 causes - A shadcn/ui Dialog stays open after the form is submitted
Dialog stays open after clicking the submit button3 causes - shadcn/ui setup fails in a Vite React project using Tailwind v4
shadcn init cannot resolve the @/ import alias4 causes - attachShadow throws NotSupportedError inside a React component
Shadow root cannot be created on a host which already hosts a shadow tree3 causes - SonarQube reports duplicated lines and fails the quality gate
Duplicated Lines (%) is high on the project overview3 causes - Storybook for a Next.js app fails to build or shows broken stories
Module not found: Error: Can't resolve 'css-loader'6 causes - React warns about a custom boolean prop on a styled-components element
Warning: Received `false` for a non-boolean attribute3 causes - Supabase says Auth session missing when a user resets a password in Next.js
AuthSessionMissingError: Auth session missing!4 causes - @svgr/webpack fails with 'Plugin name should be specified'
Error: Plugin name should be specified2 causes - Swagger UI or Swagger Editor cannot call my API or load my spec because of CORS
No 'Access-Control-Allow-Origin' header is present on the requested resource.3 causes - Swiper shows one row even though grid rows is set
Slides show in one row although grid={{ rows: 2 }} is set4 causes - T3 Env stops the build with Invalid environment variables
❌ Invalid environment variables:4 causes - Tailwind CSS 4 build fails on @apply in a Next.js project
Cannot apply unknown utility class2 causes - A Tailwind class with square brackets produces no CSS or the wrong CSS
grid-cols-[1fr 500px 2fr] has no effect3 causes - Tailwind v4 says border-border does not exist
Cannot apply unknown utility class `border-border`3 causes - Tailwind classes have no effect on a checkbox
Tailwind CSS checkbox styles are not working3 causes - Tailwind is installed but the utility classes do nothing
Utility classes such as text-3xl or bg-blue-600 have no effect in the browser5 causes - A Tailwind class does not override the class before it
className="grid flex" renders as display: grid4 causes - Tailwind's container class sticks to the left and has no padding on small screens
container is flush left on the page3 causes - A custom Tailwind color does not apply to the element
bg-brand-500 has no effect and the element stays transparent4 causes - A custom Tailwind width or height class has no effect
w-[350px] has no effect in the browser3 causes - Tailwind build says the dark: class does not exist
The `dark:` class does not exist. If `dark:` is a custom class, make sure it is defined within a `@layer` directive.3 causes - Tailwind dark mode toggled with a class has no effect
TailwindCSS v3 manual dark mode ("class") doesn't work in Next.js project4 causes - Flowbite components render but look unstyled in a Tailwind project
Flowbite buttons, cards or modals render with no colours, spacing or borders3 causes - focus:outline-none does not remove the focus border in Tailwind
focus:outline-none has no visible effect on an input3 causes - font-bold and font-light do nothing after setting a custom font family in Tailwind
font-light, font-normal and font-bold all look identical4 causes - group-focus classes in a Tailwind page do nothing when the field is focused
group-focus:opacity-100 has no effect when the field inside the group is focused4 causes - hover: on your own CSS class does nothing in Tailwind
hover:my-class has no effect3 causes - Tailwind CSS IntelliSense gives no class suggestions in a React project
No class name completions while typing inside className4 causes - mt-4 adds no space above an element in Tailwind
mt-4 on a span or a link has no visible effect3 causes - Tailwind classes from a shared package are missing in a monorepo app
Tailwind classes work in the app but not in components from a shared package3 causes - Build fails because a tool still runs PostCSS 7 and Tailwind needs 8
Error: PostCSS plugin tailwindcss requires PostCSS 8.2 causes - Tailwind md:, lg: and sm: classes do not override as expected
sm:text-center has no effect on a phone3 causes - Vite cannot resolve @tailwindcss/vite after adding Tailwind CSS
Failed to resolve "@tailwindcss/vite"3 causes - TypeScript cannot find the module @tanstack/react-query
Cannot find module '@tanstack/react-query' or its corresponding type declarations.2 causes - Jest cannot find 'react-dom/client' or '@testing-library/dom' for Testing Library
Cannot find module 'react-dom/client' from 'node_modules/@testing-library/react/dist/pure.js'2 causes - getByLabelText cannot find a label that is on the screen
Unable to find a label with the text of: Email5 causes - A React app on Tomcat shows 404 for every route except the home page
The requested resource [/myapp/dashboard] is not available4 causes - TypeScript says no overload matches a React call
No overload matches this call.3 causes - TypeScript says a module has no exported member
Module './Button' has no exported member 'Button'. ts(2305)3 causes - TypeScript 2695: left side of comma operator is unused in React code
Left side of comma operator is unused and has no side effects.ts(2695)3 causes - TypeScript cannot name the type of an exported MUI styled component
The inferred type of 'X' cannot be named without a reference to '...'. This is likely not portable. A type annotation is necessary.2 causes - Turborepo says an environment variable is not listed in turbo.json
$VARIABLE is not listed as a dependency in turbo.json4 causes - fetch() throws TypeError: Failed to fetch in the browser
TypeError: Failed to fetch4 causes - TypeScript: Cannot assign to current because it is a read-only property
Cannot assign to 'current' because it is a read-only property2 causes - TypeScript cannot find module './logo.png' or its type declarations
Cannot find module './logo.png' or its corresponding type declarations.3 causes - TypeScript cannot find the module for a .scss or CSS module import
Cannot find module './Button.module.scss' or its corresponding type declarations.3 causes - TypeScript reads a React context provider as a type, not as JSX
Cannot find namespace 'ctx'2 causes - TypeScript cannot find the type definition file for body-parser
Cannot find type definition file for 'body-parser'.2 causes - TypeScript will not let you call a function that might be undefined
error TS2722: Cannot invoke an object which is possibly 'undefined'.3 causes - TypeScript says the caught error is of type unknown
'err' is of type 'unknown'.3 causes - TypeScript says my component cannot be used as a JSX component
'Component' cannot be used as a JSX component.2 causes - TypeScript says a JavaScript module implicitly has an any type
Could not find a declaration file for module 'react-materialize'. 'path/to/module-name.js' implicitly has an 'any' type.2 causes - TypeScript rejects createRoot(document.getElementById('root'))
Argument of type 'HTMLElement | null' is not assignable to parameter of type3 causes - TypeScript refuses an array of JSX where one element is expected
Type 'Element[]' is missing the following properties from type 'Element': type, props, key2 causes - ESLint: Forbidden non-null assertion (no-non-null-assertion) in a React project
Forbidden non-null assertion2 causes - WARNING: You are running a version of TypeScript that typescript-estree does not support
WARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree3 causes - TypeScript says e.target.files is possibly null in a file input
Object is possibly 'null'.3 causes - TypeScript says a function lacks an ending return statement
error TS2366: Function lacks ending return statement and return type does not include 'undefined'.4 causes - TypeScript rejects an import that ends in .ts
An import path can only end with a '.ts' extension when 'allowImportingTsExtensions' is enabled.3 causes - TypeScript reports JSX elements as type any in a React project
JSX element implicitly has type 'any'4 causes - TypeScript says a JSX element type has no construct or call signatures
JSX element type 'X' does not have any construct or call signatures3 causes - TypeScript says a React parameter implicitly has an 'any' type
Parameter 'props' implicitly has an 'any' type.4 causes - A tsconfig paths alias is not found by TypeScript or by the build
An import such as @/components/button is underlined in the editor4 causes - TypeScript says click() is missing because the value is typed Element
Property 'click' does not exist on type 'Element'.4 causes - TypeScript: property does not exist on type IntrinsicAttributes in a React component
Property 'XXX' does not exist on type 'IntrinsicAttributes & ...'3 causes - TypeScript does not know the property you added to window
Property 'myAppConfig' does not exist on type 'Window & typeof globalThis'.2 causes - TypeScript says a property is missing on Readonly<{}> in a React class
Property 'value' does not exist on type 'Readonly<{}>'3 causes - TypeScript says property children is missing in type when you render a React component
Property 'children' is missing in type2 causes - TypeScript says a string key cannot index your object
Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'.3 causes - React Native Android red screen: Unable to load script
Unable to load script3 causes - TypeError: undefined is not iterable when destructuring a hook or array
TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator))4 causes - React warns about UNSAFE_componentWillMount in strict mode
Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code.3 causes - File uploads with UploadThing stop working after an upgrade in a Next.js app
Uploads that worked on UploadThing v6 fail after upgrading to v73 causes - Vercel function crashes with Cannot find module under /var/task/.../node_modules
Error: Cannot find module '/var/task/backend/node_modules/axios/dist/node/axios.cjs'2 causes - Django deploy on Vercel fails because Cargo (Rust) is not installed
Cargo, the Rust package manager, is not installed or is not on PATH.2 causes - My Express server deployed to Vercel answers 404 on every route
404: NOT_FOUND4 causes - Vercel fails with a function larger than the 250 MB uncompressed limit
The Vercel Function "api/hello" is 300mb uncompressed which exceeds the maximum uncompressed size limit of 250mb.4 causes - My Nuxt site on Vercel shows 500 FUNCTION_INVOCATION_FAILED
FUNCTION_INVOCATION_FAILED: Internal Server Error3 causes - Vercel blocks a deployment because the Git author has no access
Git author must have access to the project on Vercel to create deployments3 causes - A Next.js app that works locally returns 500 on Vercel
500 Internal Server Error4 causes - Vercel builds with the wrong Node.js version
The build runs a different Node.js major than the one on your machine3 causes - npm install fails with ERESOLVE during my Vercel deployment
npm ERR! code ERESOLVE3 causes - Vercel says npm run build exited with 1 and my deployment fails
Error: Command "npm run build" exited with 14 causes - Vercel says No Output Directory named dist was found after my Nuxt build
Error: No Output Directory named "dist" found after the Build completed.3 causes - My API call works locally but returns 405 after I deploy to Vercel
AxiosError: Request failed with status code 4053 causes - Swagger UI on Vercel loads blank and shows Unexpected token < in JSON
Unexpected token < in JSON at position 12 causes - Vite build passes locally but fails on Vercel with a vite/client type error
Cannot find type definition file for 'vite/client'3 causes - My Vite and React Router site returns 404 on Vercel when I refresh a page
Vercel 404 on page refresh in a Vite React app3 causes - A view-transition-name is set but nothing animates in React
The page changes instantly with no animation4 causes - Vite answers a request with 504 Outdated Optimize Dep
504 (Outdated Optimize Dep)3 causes - The @ alias for src does not work in a Vite project
Failed to resolve import "@/components/Header.vue"3 causes - The @/ import path does not resolve in Vite, Vitest or the editor
Failed to resolve import "@/components/Header.vue" from "src/App.vue". Does the file exist?4 causes - Sass prints deprecation warnings for global functions when Vite compiles Bootstrap
Deprecation warning about the global abs() function when compiling Bootstrap SCSS with Vite3 causes - Vite production build loads a blank page with 404s on its files
GET https://example.com/assets/index-<hash>.js 404 (Not Found)3 causes - npm run build fails on TypeScript errors although npm run dev worked
error TS6133: 'x' is declared but its value is never read.4 causes - Images work in vite dev but are missing after vite build
GET /assets/hero.png 404 (Not Found) after vite build4 causes - Vite will not start because Rollup's native package is missing
Error: Cannot find module @rollup/rollup-win32-x64-msvc3 causes - Vite build warns that some chunks are larger than 500 kB
(!) Some chunks are larger than 500 KiB after minification.2 causes - vite build fails with exit code 127 on a hosting build
sh: vite: command not found2 causes - Vite cannot find an entry point to scan in Docker or CI
Could not auto-determine entry point from rollupOptions or html files3 causes - vite build cannot find index.html, especially inside Docker
Could not resolve entry module (index.html)4 causes - A background image in CSS does not load in Vite
404 (Not Found) for an image or font requested through url() in CSS3 causes - Vite prints a URL but the page will not open
Local: http://localhost:5173/ (but the browser shows connection refused)4 causes - npm run dev fails or does nothing in a Vite project
vite: command not found3 causes - Vite environment variables are undefined inside a Docker container
import.meta.env.VITE_API_URL is undefined3 causes - A lazy-loaded chunk will not load in a Vite app
TypeError: Failed to fetch dynamically imported module4 causes - Vite cannot read your vite.config file
failed to load config from /path/to/project/vite.config.js3 causes - npm run dev stops with an internal PostCSS error
[vite] Internal server error: Failed to load PostCSS config2 causes - Vite cannot find the entry file named in index.html
Failed to load url /src/main.jsx (resolved id: /src/main.jsx). Does the file exist?3 causes - Vite says it failed to resolve the entry for a package in node_modules
Failed to resolve entry for package3 causes - Vite cannot find react-dom/client in main.jsx
Failed to resolve import "react-dom/client" from "src/main.jsx". Does the file exist?3 causes - Vite hot reload fails with a WebSocket connection error behind a proxy or HTTPS
WebSocket connection to 'wss://host:port/' failed4 causes - Dev server cannot reach the ASP.NET Core API in a Visual Studio SPA project
http proxy error at /weatherforecast3 causes - import.meta.env breaks or is undefined when I run my tests
Test suite failed to run3 causes - Vite build stops with [vite:load-fallback] Could not load a file
[vite:load-fallback] Could not load /src/components/Header (imported by src/App.tsx)2 causes - Vite says a Node.js module was externalized for the browser
Module "fs" has been externalized for browser compatibility. Cannot access "fs.readFile" in client code.2 causes - Vite or SvelteKit dev server works on localhost but not from another device
The page opens on localhost but a phone or another PC on the same network cannot reach it4 causes - Vite reloads the page when it finds new dependencies and an end-to-end test fails
The page reloads by itself a few seconds after the dev server starts3 causes - Vite prints "Unable to parse HTML; parse5 error code eof-in-element-that-can-contain-only-text"
Unable to parse HTML; parse5 error code eof-in-element-that-can-contain-only-text3 causes - Vite cannot find the sass preprocessor you import
Internal server error: Preprocessor dependency "sass" not found. Did you install it?2 causes - The Vite build works in preview but dist/index.html shows nothing
Blank white page when double-clicking dist/index.html3 causes - TypeScript cannot find import.meta.env in a Vite project
Property 'env' does not exist on type 'ImportMeta'.ts(2339)3 causes - The Vite dev proxy does not forward my /api requests
GET http://localhost:5173/api/users 404 (Not Found)5 causes - Vite dev proxy fails against a local API with a self-signed certificate
Requests to a local HTTPS API fail with a self-signed certificate error3 causes - React page is blank when a backend serves the HTML for Vite
Uncaught Error: @vitejs/plugin-react can't detect preamble. Something is wrong.3 causes - Vite dev server returns 403 for a file outside the allow list
The request url "/path/to/file" is outside of Vite serving allow list.3 causes - Vite says the module has no export named 'default'
Uncaught SyntaxError: The requested module '/src/utils.js' does not provide an export named 'default'3 causes - vite build stops with Rollup failed to resolve import
[vite]: Rollup failed to resolve import "x" from "src/main.js".3 causes - Vite warns about a script tag in index.html it cannot bundle
<script src="..."> in "/index.html" can't be bundled without type="module" attribute3 causes - The Vite dev server takes a long time to start or load the first page
npm run dev takes tens of seconds before the page appears4 causes - A Vite single page app shows 404 when you refresh a route on the live site
404 Not Found when you refresh /about or open a deep link3 causes - The browser got an HTML page where a Vite script should be
Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html".3 causes - An SVG imported in Vite renders as a URL, not as a component
Element type is invalid: expected a string (for built-in components) or a class/function but got: string.4 causes - Decorators fail in a Vite and TypeScript 5 project
A decorator that worked before is rejected by the type checker after moving to TypeScript 53 causes - Vite dev and build pass even though the Vue TypeScript code has type errors
The editor shows red type errors but npm run dev and npm run build succeed3 causes - Node.js warns that util._extend is deprecated when running Vite or Vue tooling
DeprecationWarning: The `util._extend` API is deprecated. Please use Object.assign() instead2 causes - Images from a computed path break after vite build in Vue
Image shows in npm run dev but is missing or undefined after npm run build3 causes - Vuetify build fails on a Sass variable that is not configurable
Error: This variable was not declared with !default in the @used module.2 causes - Vitest ignores environment: 'jsdom' and still runs tests in Node
typeof window is 'undefined' inside a test3 causes - TypeScript rejects the test block in vite.config.ts
'test' does not exist in type 'UserConfigExport'2 causes - VS Code shows no ESLint errors after moving to eslint.config.js
npx eslint . prints errors but the editor shows no squiggles4 causes - VS Code cannot load or install extensions: XHR failed
XHR failed4 causes - VS Code does not autocomplete or follow a Vite alias like @/
import from '@/components/Button' builds fine but is not resolved in the editor3 causes - A Vue image with a dynamic src shows a broken link in a webpack build
404 (Not Found) on the image request4 causes - Fonts on another domain are blocked by CORS (nginx and Apache)
Font from origin has been blocked from loading by Cross-Origin Resource Sharing policy4 causes - webpack stops with 'You may need an additional loader to handle the result of these loaders'
Module parse failed: Unexpected character4 causes - webpack-dev-server fails to start with a missing webpack/bin file
Error: Cannot find module 'webpack/bin/config-yargs'2 causes - webpack does not find your .ts and .tsx files
Module not found3 causes - webpack cannot find style-loader or another loader
Error: Cannot resolve module 'style-loader'3 causes - A Chrome extension built with webpack is blocked for using eval
unsafe-eval3 causes - webpack lazy-loaded chunk fails to load (ChunkLoadError)
ChunkLoadError: Loading chunk 123 failed.3 causes - The browser blocks a request from webpack-dev-server with a CORS error
CORS header 'Access-Control-Allow-Origin' missing4 causes - The webpack dev server client reports it is disconnected and stops reloading
[WDS] Disconnected!3 causes - Invalid Host header from webpack-dev-server
Invalid Host header3 causes - webpack-dev-server says the options object does not match the API schema
Invalid options object. Dev Server has been initialized using an options object that does not match the API schema.4 causes - webpack cannot find its entry file ./src/index.js
Module not found: Error: Can't resolve './src/index.js' in '/home/user'3 causes - webpack: external type 'module' used in a script that has no dynamic import()
webpack build fails for an external of type module in a script bundle4 causes - Webpack warns Failed to parse source map from a dependency
Failed to parse source map3 causes - webpack says the configuration object does not match the API schema
Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.3 causes - webpack warns about importing a named export from a JSON file
Should not import the named export 'version' (imported as 'version') from default-exporting module (only default export is available soon)2 causes - Module Federation fails with: Module does not exist in container
Module "./Button" does not exist in container3 causes - Module Federation app crashes on start with 'Shared module is not available for eager consumption'
Uncaught Error: Shared module is not available for eager consumption2 causes - webpack build fails on fs, path or node:crypto in browser code
Module not found: Error: Can't resolve 'fs'3 causes - webpack cannot resolve an import (Module not found)
Module not found: Error: Can't resolve './components/Header' in '/app/src'4 causes - webpack 5 cannot resolve an import that has no file extension
Module not found3 causes - The browser rejects fonts built by webpack with OTS parsing error
OTS parsing error3 causes - process.env.MY_VAR is undefined in my webpack browser bundle
process.env.API_URL is undefined in the browser4 causes - Script fails with MIME type text/html on a nested route in a webpack app
Refused to execute script from 'http://localhost:8080/users/bundle.js' because its MIME type ('text/html') is not executable, and strict MIME type checking is enabled.2 causes - A path alias works in the editor but not in the webpack build
Module not found4 causes - webpack rejects a rule that mixes resource with test, include or exclude
Error: Rule can only have one resource source (provided resource and test + include + exclude)3 causes - Browser devtools show bundled code instead of my original files
Devtools show bundle.js or main.js instead of the original source files2 causes - Unexpected token 'export' when you build or run JavaScript
SyntaxError: Unexpected token 'export'2 causes - WebSocket connection to ws://localhost:3000/ws failed for a React dev server behind nginx or Docker
WebSocket connection to 'ws://localhost:3000/ws' failed4 causes - The browser refuses a ws:// connection opened from your HTTPS React app
Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.4 causes - InvalidStateError when calling send() on a new WebSocket
Uncaught InvalidStateError: Failed to execute 'send' on 'WebSocket': Still in CONNECTING state2 causes - WordPress media upload fails with "Unexpected response from the server"
Unexpected response from the server. The file may have been uploaded successfully. Check in the Media Library or reload the page.3 causes - Socket.IO client fails to connect with xhr poll error
Error: xhr poll error4 causes - Yup conditional validation throws branch is not a function
TypeError: branch is not a function2 causes - TypeScript rejects the is/then/otherwise object in Yup when()
'is' does not exist in type 'ConditionBuilder<StringSchema<string, AnyObject, undefined, "">>'2 causes - A Zod refinement error does not appear or does not clear in React Hook Form
The confirm password error stays after the password is fixed4 causes
Next step
Something here keeps breaking?
I fix these for clients and run the same stack in production myself.