ReferenceError: WebSocket is not defined (Node.js, 2026)

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 see ReferenceError: WebSocket is not defined. The fixes: upgrade to Node 22+, use the long-standing ws package, or pull from undici.

Step 1: Check Node version

node --version
# v22+ = WebSocket is a global (client only, no server)
# v21 and older = use ws or undici

Fix 1: Upgrade to Node 22+

nvm install 22
nvm use 22

// Then no code change needed:
const ws = new WebSocket('wss://echo.websocket.org');

ws.addEventListener('open', () => ws.send('hello'));
ws.addEventListener('message', (event) => console.log(event.data));
ws.addEventListener('close', () => console.log('closed'));

Fix 2: Use the ws package (battle-tested)

npm install ws

import WebSocket from 'ws';

const ws = new WebSocket('wss://echo.websocket.org');

ws.on('open', () => ws.send('hello'));
ws.on('message', (data) => console.log(data.toString()));
ws.on('close', () => console.log('closed'));

Fix 3: Build a server with ws

// Built-in WebSocket in Node 22+ is CLIENT only.
// For a server, you still need ws:

import { WebSocketServer } from 'ws';

const wss = new WebSocketServer({ port: 8080 });

wss.on('connection', (socket) => {
  socket.on('message', (data) => {
    socket.send(`Echo: ${data}`);
  });
});
console.log('WebSocket server on :8080');

Fix 4: undici client (alternative)

npm install undici

import { WebSocket } from 'undici';

const ws = new WebSocket('wss://echo.websocket.org');
ws.addEventListener('open', () => ws.send('hello'));

Debugging checklist for ReferenceError

Before diving into fixes, run through this diagnostic checklist. Nine times out of ten the answer surfaces here.

1. Read the full traceback, not just the error message. The stack trace shows exactly which line and which call chain triggered the error. The last line names the immediate cause; earlier lines show how you got there.
2. Add print or debug statements just before the failing line. Print the variable, its type, and its value. Nine out of ten error surprises come from the value being different from what you assumed.
3. Check JavaScript / Node.js version compatibility. Errors sometimes result from APIs that changed between versions. Run your interpreter version check and compare against the library documentation for that version.
4. Isolate the failing call in a minimal reproducer. Copy the failing line into a small standalone script with hardcoded inputs. If it fails there too, the bug is in your code. If not, something in your surrounding context is contributing.
5. Search the exact error message. Include the class name and the specific text in your search. Chances are someone else hit the same issue and the fix is documented on Stack Overflow or the library’s GitHub issues.

Common causes for ReferenceError

Most instances of this error trace back to one of these root causes:

• Uninitialized or missing input. A variable was not populated before use, or the input source (file, API response, database row) did not contain the expected key or value.
• Type mismatch. The code expected a specific type (dict, list, string) but received something different. JavaScript / Node.js’s dynamic typing means this often surfaces at runtime, not at compile time.
• Version drift. The library API changed and your code assumes the old signature. Check the library’s changelog for breaking changes since the version you last used.
• Race condition or ordering issue. Async or concurrent code sometimes tries to access data before it is ready. Add awaits, locks, or explicit ordering to fix.
• Copy-paste from stale tutorial. Older tutorials may use APIs that no longer exist. Always check the official docs for the current version.

Testing and prevention

Preventing this class of error from recurring is more valuable than fixing it once. Build these habits into your workflow:

• Write tests that trigger the error path. If your test suite hits the error scenario, catch and assert it. A well-written test prevents the same bug from returning.
• Validate inputs at API boundaries. When data enters your code from external sources (HTTP requests, file uploads, database queries), validate structure and types immediately.
• Use type hints and static analysis. Tools like mypy for Python or TypeScript for JavaScript catch many type mismatches before you run the code.
• Log important state. Structured logging with context helps you debug production issues faster. Include enough context to reconstruct what happened.
• Read the library changelog. Before upgrading a dependency, skim the changelog for breaking changes. Two minutes of reading saves an hour of debugging.

When to ask for help

Some errors are worth solving yourself for the learning. Others are worth asking about early. Ask for help when: the error blocks a customer-facing feature, you have spent an hour without progress, the error involves security or data integrity, or you are unsure whether your fix will introduce new bugs. Post to Stack Overflow with a minimal reproducer, or ask a senior developer on your team. Time boxes are your friend.

Production hardening for ReferenceError

Fixing ReferenceError once is not enough. To prevent it from recurring in production, harden the surrounding code with these patterns.

• Defensive coding at API boundaries. Every function that receives external data (HTTP requests, database rows, file uploads, third-party API responses) should validate structure and types before proceeding. Use validation libraries like Pydantic (JavaScript specific) to enforce schemas at the boundary.
• Structured logging with context. When ReferenceError occurs, your logs should include enough context to reconstruct the failure. Include the operation name, input values, user or request ID, and the full stack trace. Avoid logging sensitive data (passwords, tokens, PII).
• Error monitoring and alerting. Tools like Sentry, Rollbar, or Datadog capture production errors with stack traces and context. Set up alerts for ReferenceError so you know within minutes when it happens in production.
• Retry logic with exponential backoff. For transient errors (network failures, temporary API errors), retry with 1-second, 2-second, 4-second delays. Cap at 3-5 retries to prevent infinite loops.
• Circuit breakers for external dependencies. If an external service repeatedly fails, stop calling it for a period and return a fallback response. Prevents cascading failures.

Testing strategies to catch ReferenceError early

Investing in tests that specifically trigger the error path prevents regressions. Build these into your test suite:

• Unit tests for the failing function. Write a test that reproduces the exact conditions that caused ReferenceError. If your test fails, your fix works. If your test passes with the buggy code, your test is not testing the right thing.
• Property-based testing. Tools like Hypothesis for Python generate random inputs and check invariants hold. Great for catching edge cases you did not think of.
• Integration tests with real dependencies. Mock-heavy unit tests miss real-world issues. Have at least one integration test that hits a real database, API, or file system.
• Continuous integration. Run your test suite on every pull request. Catch bugs before they reach main.