Error: ENOENT No Such File or Directory in Nodejs

Introduction

When working with file operations in Node.js, it’s almost inevitable that you’ll bump into the ENOENT No Such File or Directory in Node.js error at some point. This Node.js missing file error usually surfaces when you try to access, read, or write a file that doesn’t exist at the specified path. A typical error trace looks like:

Error: ENOENT: no such file or directory, open 'data.json'
    at Object.openSync (fs.js:479:3)
    at fs.readFileSync (fs.js:380:35)
    at Object.<anonymous> (/path/to/app/index.js:5:10)
    …

Error: ENOENT: no such file or directory, open 'data.json'
    at Object.openSync (fs.js:479:3)
    at fs.readFileSync (fs.js:380:35)
    at Object.<anonymous> (/path/to/app/index.js:5:10)
    …

In this deep-dive guide, we’ll cover:

What ENOENT stands for and why it happens
Common scenarios that trigger Error: ENOENT No Such File or Directory in Node.js
Real code examples demonstrating the mistake and the fix
Step-by-step solutions using fs.existsSync(), path.join(), and proper error handling
Debugging tips for Node.js file system errors
FAQs on ENOENT errors and best practices

By the end, you’ll have a solid strategy to diagnose and fix ENOENT Node.js errors in your projects.

What Is ENOENT No Such File or Directory in Node.js?

“ENOENT” is shorthand for Error NO ENTry, indicating that a file or directory does not exist. It is one of the most common Node.js file system errors you’ll see when using the built-in fs module:

Error Code: ENOENT
Meaning: The target file or directory was not found
Common Contexts: fs.readFile, fs.writeFile, fs.stat, fs.unlink, fs.readdir, and other fs APIs

A simple example:

// index.js
import fs from 'fs';
const content = fs.readFileSync('missing.json', 'utf8');
console.log(content);

// index.js
import fs from 'fs';

const content = fs.readFileSync('missing.json', 'utf8');
console.log(content);

Running this will throw:

Error: ENOENT: no such file or directory, open 'missing.json'

Error: ENOENT: no such file or directory, open 'missing.json'

This happens because there’s no file named missing.json in your working directory.

Common Scenarios That Trigger ENOENT No Such File or Directory in Node.js

Understanding typical triggers helps you prevent the ENOENT No Such File or Directory in Node.js error from recurring.

1. Using fs.readFile or fs.writeFile with a Wrong Path

import fs from 'fs';
fs.readFile('data/data.json', 'utf8', (err, data) => {
  if (err) throw err; // ENOENT if path is wrong
  console.log(data);
});

import fs from 'fs';

fs.readFile('data/data.json', 'utf8', (err, data) => {
  if (err) throw err; // ENOENT if path is wrong
  console.log(data);
});

If data/data.json doesn’t exist or path is misspelled → ENOENT.

2. Trying to Read a File Before It’s Created

import fs from 'fs';
fs.writeFileSync('output.txt', 'Hello, world!');
// Oops, trying to read from a file we thought we created:
const text = fs.readFileSync('output1.txt', 'utf8');

import fs from 'fs';

fs.writeFileSync('output.txt', 'Hello, world!');
// Oops, trying to read from a file we thought we created:
const text = fs.readFileSync('output1.txt', 'utf8');

Typo in filename (output1.txt instead of output.txt) → ENOENT.

3. Incorrect Relative vs. Absolute Path

// index.js located at /project/src/index.js
import fs from 'fs';
// This is relative to process.cwd(), not file location!
const data = fs.readFileSync('./config.json', 'utf8');

// index.js located at /project/src/index.js
import fs from 'fs';

// This is relative to process.cwd(), not file location!
const data = fs.readFileSync('./config.json', 'utf8');

If setup.js expects files relative to /project/scripts but you’re running it from /project, relative imports (e.g. ./templates/default.json) will misresolve.

Example 1: Reading a Missing File

Let’s demonstrate fs.readFile ENOENT Node.js in action:

// read-example.js
import fs from 'fs';
fs.readFile('data.json', 'utf8', (err, content) => {
  if (err) {
    console.error('Read failed:', err);
    return;
  }
  console.log('File content:', content);
});

// read-example.js

import fs from 'fs';

fs.readFile('data.json', 'utf8', (err, content) => {

  if (err) {

    console.error('Read failed:', err);

    return;

  }

  console.log('File content:', content);

});

Run it:

node read-example.js

node read-example.js

Error output:

Read failed: Error: ENOENT: no such file or directory, open 'data.json'
    at Object.openSync (fs.js:462:3)
    at Object.readFileSync (fs.js:360:35)
    at FSReqCallback.readFileAfterClose [as oncomplete] (fs.js:447:12)

Read failed: Error: ENOENT: no such file or directory, open 'data.json'

    at Object.openSync (fs.js:462:3)

    at Object.readFileSync (fs.js:360:35)

    at FSReqCallback.readFileAfterClose [as oncomplete] (fs.js:447:12)

Explanation:

Node attempts to open data.json in the current working directory
The file isn’t found → err.code === ‘ENOENT’
Without guarding against it, your application crashes or logs an unhelpful stack trace

Conclusion

The ENOENT No Such File or Directory in Node.js error is a classic stumbling block in file I/O. By understanding that ENOENT means Error NO ENTry, adopting absolute path resolution (path.join(__dirname, …)), checking for file existence (fs.existsSync, fs.accessSync), and implementing thorough error handling, you can eliminate most occurrences of this Node.js missing file error.

With these debugging fs errors in node tips and code patterns, your applications will handle missing files gracefully, improving reliability both in development and production. Always validate paths, catch errors, and log clear messages—your future self (and your users) will thank you!