Exception in nodemon killing node referenceerror: primordials is not defined

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 article will examine the underlying reasons behind this exception and provide practical solutions to effectively resolve it.

But before that, let’s understand what is nodemon…

What is Nodemon?

Nodemon, also known as “node monitor,” is a widely used tool in the Node.js community.

It allows for automatic restarting of Node.js applications whenever there are changes made to files within a specific directory.

This convenient feature eliminates the manual task of restarting applications after each modification, which ultimately saves developers time and effort.

What is Exception in nodemon killing node referenceerror: primordials is not defined?

The error message “Exception in nodemon killing node referenceerror: primordials is not defined,” is telling us that something went wrong while using nodemon.

The Nodemon is a helpful tool for automatically restarting a Node.js application whenever we make changes to our files.

In this case, the error is specifically related to a problem with the “primordials” reference.

This could be a module or object that should be available but is not being found.

Additionally, the error often occurs when there is a mismatch between the version of Node.js we’re using and the dependencies installed.

The most common reason for this error is that the project’s dependencies are not compatible with the version of Node.js being used.

It usually happens when the project relies on an older version of a package that depends on a specific feature called “primordial.”

However, this feature was removed in newer versions of Node.js, leading to the error message you encountered.

Example of Exception in nodemon killing node referenceerror

Here’s an example of a program that may encounter the “Exception in nodemon killing node referenceerror: primordials is not defined” error:

const http = require('http');

const server = http.createServer((req, res) => {
  res.writeHead(200, { 'Content-Type': 'text/plain' });
  res.end('Hello, world!');
});

server.listen(3000, 'localhost', () => {
  console.log('Server is running on port 3000');
});

When you try to run this program using Nodemon, you might encounter the “Exception in nodemon killing node referenceerror: primordials is not defined” error.

This error typically occurs due to conflicts or compatibility issues with the dependencies.

How to fix Exception in nodemon killing node referenceerror: primordials is not defined?

Anyway besides this error, we also have fixed errors that you can check which might help you when you encounter them.

• Referenceerror: response is not defined
• Reference error: navigator is not defined
• Referenceerror request is not defined

Conclusion

In conclusion, “Exception in nodemon killing node referenceerror: primordials is not defined” typically occurs when there are compatibility issues or conflicts with dependencies, specifically related to the “primordials” module.

This error often arises when using older versions of Node.js or NPM, or when there are inconsistencies in the project’s dependencies.

I think that’s all for this error. We hope this article has helped fix the issues.

Until next time! 😊

Node.js ReferenceError patterns

Node.js ReferenceErrors usually come from missing require/import statements, ES module vs CommonJS mismatch, or trying to use browser globals (window, document) that do not exist in Node.

Common triggers

• ES modules vs CommonJS. require is CommonJS; import is ESM. Files ending .mjs or with "type": "module" in package.json use ESM only.
• Missing global-like modules. fetch was added natively in Node 18. Older Node needs import fetch from 'node-fetch';.
• Browser globals in Node. window, document, localStorage do not exist. Use Node equivalents or polyfills.
• __dirname and __filename in ES modules. Not available — derive from import.meta.url.
• process not defined in ES modules of browser context. Node.js process global is not automatically shimmed in bundlers.

Diagnostic pattern

// BAD — mixing require and ES module context
// package.json has "type": "module"
const fs = require('fs');  // ReferenceError: require is not defined

// GOOD — use ES import
import fs from 'node:fs';
import path from 'node:path';

// __dirname replacement in ES modules
import { fileURLToPath } from 'node:url';
import { dirname } from 'node:path';
const __filename = fileURLToPath(import.meta.url);
const __dirname = dirname(__filename);

Best practices

• Pick ESM or CommonJS per project. Not both — Node 20+ handles ESM well.
• Use node:fs prefix. Explicit built-in modules are clearer.
• Upgrade to Node 20 LTS. Latest features + long support window.
• Use TypeScript for larger projects. Catches ReferenceErrors before runtime.

Glay Eliver

Programmer & Technical Writer at PIES IT Solution

Glay Eliver is a programmer and writer at PIES IT Solution, author of over 600 tutorials at itsourcecode.com. Specializes in JavaScript tutorials, Microsoft Office how-tos (Excel, Word, PowerPoint), and Python error debugging covering ImportError, TypeError, AttributeError, ModuleNotFoundError, and JavaScript ReferenceError. Authored several of the site’s highest-traffic Excel and MS Office reference articles.

Expertise: JavaScript · MS Excel · MS Word · MS PowerPoint · Python · Python ImportError · Python TypeError · Python AttributeError · ModuleNotFoundError · JavaScript ReferenceError · Pygame
 · View all posts by Glay Eliver →