Referenceerror request is not defined
In this article, we will delve into the ReferenceError with a specific focus on the error message “ReferenceError: Request is not defined.” We will explore its definition, common causes, and …
JavaScript ReferenceError Reference: 34+ “X is not defined” Fixes (2026)
itsourcecode.com hosts 34+ documented fixes for JavaScript ReferenceError messages: the error class raised when JavaScript tries to access a variable, function, or global that doesn’t exist in the current scope. Most ReferenceErrors come from SSR vs browser context mismatches (window, document, navigator on server), ES Module vs CommonJS confusion (__dirname, require, module), Node.js version migrations (primordials, fetch), or library loading order (React, Jest, Google Maps). Browse the fixes below.
What is a JavaScript ReferenceError?
A ReferenceError is raised when JavaScript tries to read a variable or identifier that hasn’t been declared in any reachable scope. It’s distinct from TypeError (the value exists but has the wrong type) and from SyntaxError (the code couldn’t be parsed). Most ReferenceErrors are “X is not defined”, and the fix usually involves either declaring/importing X, or running the code in the right environment where X already exists as a global.
How to debug any ReferenceError in 4 steps
Read the missing identifier in the message. ReferenceError: X is not defined tells you exactly what’s missing.
Determine the runtime context. Browser globals (window, document, navigator, fetch in older Node) don’t exist server-side. Node-only globals (process, __dirname, require) don’t exist in browsers OR in Node ES modules. Frameworks like Next.js/Nuxt/Remix run code in BOTH contexts.
Check the module type. If you see __dirname is not defined in ES module scope, you’re in an ESM file. Use import.meta.url + fileURLToPath instead. If require is not defined, same issue, opposite direction.
Check load order. If the missing name is a library global ($, React, google, jest), the library hasn’t loaded yet. Check script tag order, or import explicitly.
Featured ReferenceError fixes by category
🌐 Browser globals on server (SSR / Node)
The single most common ReferenceError class for modern web devs. Server has no window, document, or navigator.
Uncaught ReferenceError: X is not defined
ReferenceError: navigator is not defined
Uncaught ReferenceError: function is not defined
📦 ES Modules: Node.js
Node 12+ supports ES modules. Switching from CommonJS to ESM breaks names that ESM doesn’t expose globally.
__dirname is not defined in ES module scope
exports is not defined in ES module scope
Uncaught ReferenceError: exports is not defined
Uncaught ReferenceError: global is not defined (browser)
Uncaught ReferenceError: process is not defined
ReferenceError: Buffer is not defined (browser bundlers)
ReferenceError: globalThis is not defined
⚛️ React / Next.js / build tools
ReferenceError: React is not defined (JSX without import)
ReferenceError: Jest is not defined, 2026 Guide
ReferenceError: primordials is not defined
Exception in nodemon: primordials is not defined
📡 Network / Request globals
ReferenceError: request is not defined
ReferenceError: response is not defined
ReferenceError: File is not defined (Node before File API)
🗺️ Library/CDN globals (Google Maps, etc.)
Uncaught ReferenceError: google is not defined (Maps API)
Related error categories
ReferenceError is one of 10 hubs in our Python & JavaScript error reference cluster, 980+ documented fixes total:
TypeError Reference, 220+ Python & JS TypeError fixes
ModuleNotFoundError Reference, 198+ Python import errors
AttributeError Reference, 173+ “object has no attribute X” fixes
ValueError Reference, 100+ pandas/NumPy/sklearn fixes
ImportError Reference, 67+ “cannot import name X from Y” fixes
NameError Reference, 49+ Python “name X is not defined” fixes
RuntimeError Reference, 49+ PyTorch/CUDA/async runtime errors
SyntaxError Reference, 48+ Python & JavaScript syntax errors
HTTP Error Reference, 35+ HTTP status code fixes (4xx, 5xx)
Python Tutorial, beginner-to-intermediate Python lessons
About this ReferenceError reference
Built since 2015 by PIES Information Technology Solutions, Binalbagan, Negros Occidental, Philippines. Every post comes from a real error encountered in production code. Used by 12,000+ developers monthly.
Reference error: navigator is not defined
Have you encountered the “Reference error: navigator is not defined” message when working with JavaScript? This error can be particularly bothersome when developing a JavaScript-dependent website or application. In this …
Referenceerror: response is not defined
Programmers often come across the common error known as “ReferenceError: response is not defined” while working with JavaScript or other programming languages. This error occurs when the code tries to …
Uncaught referenceerror: process is not defined
Many developers often face a specific error called “Uncaught referenceerror: process is not defined.” This error can be quite perplexing and frustrating, especially for beginners in programming. In this article, …
Referenceerror: globalthis is not defined
Many developers often face a specific error called “ReferenceError: globalThis is not defined.” This error can be quite perplexing and frustrating, especially for beginners in programming. In this article, we …
Uncaught referenceerror: global is not defined
The “Uncaught ReferenceError: global is not defined” error is a common occurrence in programming. It indicates that there’s an attempt to reference a variable or object called “global,” but it …
Uncaught referenceerror: browser is not defined
This article focuses on the “Uncaught ReferenceError browser is not defined” error in JavaScript, which is commonly encountered in web development. It explains why this error occurs along with its …
[Fixed] ReferenceError: Textencoder Is Not Defined — JS 2026
This article focuses on the “Referenceerror: textencoder is not defined” error in JavaScript, which is commonly encountered in web development. Specifically, it addresses why this error occurs and provides practical …
Referenceerror buffer is not defined
Have you encountered a “ReferenceError: buffer is not defined” error? Which indicates an issue with a variable or object reference? Well when working with JavaScript or any programming language, encountering …
Referenceerror: regeneratorruntime is not defined
In this detailed guide, we will explore the error message “Uncaught ReferenceError: regeneratorRuntime is not defined“. At the same time, we will investigate the reasons behind this error and offer …
[Fixed] ReferenceError: Module Is Not Defined In Es Module Scope — JS 2026
When working with ES Modules, you may encounter the “ReferenceError: module is not defined in ES module scope” error. This article explores the causes of this error and offers solutions …
Referenceerror: self is not defined
When working with JavaScript, encountering errors is a common occurrence for developers. One such error that often puzzles programmers is the “ReferenceError: self is not defined.” In this article, we …
Uncaught referenceerror: wp is not defined
One particular error that can be quite frustrating is the “Uncaught ReferenceError: wp is not defined.” This error commonly happens when JavaScript code refers to an object or variable that …
Frequently Asked Questions
What is the difference between ReferenceError and TypeError?
ReferenceError means the identifier does not exist at all in any scope JavaScript can reach. TypeError means the identifier exists but the value has the wrong type for what you tried to do (calling a non-function, reading a property of undefined). If you see "is not defined", ReferenceError. If you see "is not a function" or "cannot read property X of undefined", TypeError.
Why does "window is not defined" happen on the server?
You are running code in Node.js (SSR, build step, API route) where there is no browser. window only exists in browsers. Three fixes: (1) Check typeof window !== 'undefined' before using it. (2) For Next.js, move the code into useEffect (runs only on client). (3) Use dynamic imports with { ssr: false } for whole client-only components.
Why does "__dirname is not defined" happen in ES modules?
ESM does not expose __dirname or __filename as globals (they are CommonJS-only). To get the current file's directory in ESM, use: import { fileURLToPath } from 'url'; import path from 'path'; const __dirname = path.dirname(fileURLToPath(import.meta.url));
Why does "process is not defined" happen in the browser?
process is a Node.js global; browsers do not have it. If your bundled code references process.env.X, configure your bundler to replace process.env at build time: Vite does this automatically with import.meta.env; Webpack needs DefinePlugin; Next.js exposes NEXT_PUBLIC_* env vars to the browser.
Why does "ReferenceError: React is not defined" happen?
You are using JSX in a file that does not import React. Either: (1) Add import React from 'react' at the top. (2) Configure your React 17+ runtime, set jsx: 'react-jsx' in tsconfig.json, or use @babel/preset-react with { runtime: 'automatic' }. The automatic runtime imports React for you.
How do I prevent ReferenceError in production?
(1) Use TypeScript or JSDoc with type-checking, they catch undefined references at compile time. (2) Use a linter (ESLint with no-undef rule). (3) For SSR frameworks, follow the framework's pattern for "client-only" code. (4) Always check typeof X !== 'undefined' before using suspected globals.
How often is this ReferenceError reference updated?
New posts are added weekly. Last refreshed: May 2026. Note: 2 posts (window-is-not-defined, cannot-access-before-initialization) were removed in our May 2026 content quality cleanup, their replacements may return as fully-rewritten guides in the future.