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.
The URL constructor lets you parse and build URLs cleanly: new url(/sitelet?url=https%3A%2F%2Fitsourcecode.com%2Ftopics%2Freferenceerror%2F%25E2%2580%2598https%3A%2F%2Fitsourcecode.com%2Fpath%25E2%2580%2599) gives you .host, .pathname, .searchParams properties. It is global in modern Node and browsers, but old IE11 and …
atob (“ASCII to binary”) decodes Base64 and btoa encodes it. Browsers had them forever; Node only added them as globals in v16. If you see ReferenceError: atob is not defined …
Browsers have had WebSocket as a global since 2011. Node.js shipped it as a stable global in v22 (late 2024). If you are on Node 21 or older, you will …
The Headers class is one of the WhatWG Fetch interfaces. Like fetch and FormData, it was a browser global for years but only landed in Node.js with v18. If you …
FormData is the multipart request body class that handles file uploads and form submissions. Browsers have always had it. Node.js added it natively in v18. Older Node throws ReferenceError: FormData …
structuredClone() is the built-in deep-clone function that handles Map, Set, Date, RegExp, ArrayBuffer, and circular references. It works in modern browsers and Node 17+. If you see ReferenceError: structuredClone is …
AbortController lets you cancel fetch requests and timers. It was added natively to Node.js in v15. If you are on Node 14 or older, you will see ReferenceError: AbortController is …
The browser had fetch from day one, but Node.js only added it natively in v18. If you are on Node 16 or older, you will hit ReferenceError: fetch is not …
The classic ReferenceError: window is not defined hits every JavaScript developer who tries server-side rendering (SSR) for the first time. The browser window object simply does not exist in Node.js, …
The crypto object means different things on the server and in the browser. On Node, it was a require-only module until v19 (when crypto became a global), and the browser-style …
When transitioning from the CommonJS module system to ES modules, developers may encounter the “ReferenceError: __dirname is not defined in ES module scope” error. Wherein modern JavaScript development, the adoption …
One of the most common mistakes that developers often come across in JavaScript is the “Uncaught ReferenceError is not defined” error. In this article, we will explore the complexities of …
Developers working with Node.js, have instances encounter errors like “Exception in Nodemon: Killing Node ReferenceError: Primordials is not Defined“. Which can lead to confusion and impede the development workflow. This …