Node.js ENOENT

What It Means

ENOENT stands for “Error NO ENTry” (or “No such file or directory”). This error occurs when Node.js tries to access a file or directory that doesn’t exist at the specified path. It can come from fs operations, require(), child_process.exec(), or any operation that accesses the filesystem.

Common Causes

• File or directory path is incorrect or has a typo
• Relative path resolved from an unexpected working directory
• File was deleted, moved, or never created
• Path separators wrong for the operating system
• npm install hasn’t been run (missing node_modules)
• Build artifacts haven’t been generated yet
• Environment-specific paths that don’t exist in production

How to Fix

Check the path

const path = require('path');
const fs = require('fs');

// Check what path is being resolved
const filePath = './config/settings.json';
console.log('Resolved path:', path.resolve(filePath));
console.log('CWD:', process.cwd());
console.log('Exists:', fs.existsSync(filePath));

Use __dirname for reliable paths

const path = require('path');

// Bad: relative to process.cwd(), which varies
const config = require('./config/settings.json');

// Good: relative to the current file
const configPath = path.join(__dirname, 'config', 'settings.json');
const config = require(configPath);

// ES Modules equivalent
import { fileURLToPath } from 'url';
import { dirname, join } from 'path';

const __filename = fileURLToPath(import.meta.url);
const __dirname = dirname(__filename);
const configPath = join(__dirname, 'config', 'settings.json');

Handle the error gracefully

const fs = require('fs/promises');

// Using async/await
try {
  const data = await fs.readFile('/path/to/file.json', 'utf-8');
  return JSON.parse(data);
} catch (error) {
  if (error.code === 'ENOENT') {
    console.log('File not found, using defaults');
    return { default: true };
  }
  throw error;
}

Create file/directory if missing

const fs = require('fs');
const path = require('path');

// Create directory recursively
const dir = path.join(__dirname, 'logs', 'app');
fs.mkdirSync(dir, { recursive: true });

// Create file with default content if it doesn't exist
const configPath = path.join(__dirname, 'config.json');
if (!fs.existsSync(configPath)) {
  fs.writeFileSync(configPath, JSON.stringify({ port: 3000 }, null, 2));
}

Fix child_process ENOENT

const { execSync, spawn } = require('child_process');

// ENOENT from spawn means the command wasn't found
try {
  const child = spawn('nonexistent-command', ['arg']);
  child.on('error', (err) => {
    if (err.code === 'ENOENT') {
      console.error('Command not found. Is it installed?');
    }
  });
} catch (error) {
  if (error.code === 'ENOENT') {
    console.error('Command not found');
  }
}

// Fix: use full path or ensure command is in PATH
const child = spawn('/usr/bin/python3', ['script.py']);

// Or on Windows, use shell: true
const child = spawn('dir', [], { shell: true });

Fix npm ENOENT

# Missing node_modules
npm install

# Missing package-lock.json
npm install  # Creates it

# Missing script referenced in package.json
# Check that the script file actually exists
node -e "console.log(require('./package.json').scripts)"

Related Errors

• Node.js EPERM - File exists but operation is not permitted.
• Node.js EACCES - File exists but access is denied.
• Node.js ERR_MODULE_NOT_FOUND - ES module could not be found.