How to fix Error: Cannot find module './index' in Node.js

Node.jsBEGINNERMEDIUMUpdated Dec 9, 2025· 118 views

This error occurs when Node.js attempts to import a directory but cannot locate an index.js file or a valid entry point specified in package.json. It typically happens when directory imports rely on implicit index file resolution.

Quick fix

Fixes MODULE_NOT_FOUND

# Navigate to the directory being imported
ls -la ./path/to/directory

# Check if index.js exists
test -f ./path/to/directory/index.js && echo "File exists" || echo "File missing"
  1. Verify the directory structure and locate the missing index.js file
  2. Create the missing index.js file if needed
  3. Check and fix package.json main field if present
  4. Update import statements to reference specific files
node.js — error
# Navigate to the directory being imported
ls -la ./path/to/directory
# Check if index.js exists
test -f ./path/to/directory/index.js && echo "File exists" || echo "File missing"
Error: Cannot find module './index'

What this error means

This error indicates that Node.js's module resolution system attempted to load a directory as a module but failed to find the expected entry file. When you require or import a directory path in Node.js, the module system follows a specific resolution algorithm: it first checks for a package.json file with a "main" field pointing to an entry file, then falls back to looking for index.js, index.json, or index.node files in that directory. When none of these files exist or the "main" field points to a non-existent file, Node.js cannot determine how to load the module and throws this error. This is a fundamental part of Node.js's CommonJS module resolution system, which assumes directories being imported as modules must have a clear entry point. The error message typically includes the relative or absolute path to the directory that Node.js attempted to load, helping you identify which import statement is causing the problem.

Typical symptoms

  • Application crashes on startup with "Cannot find module './index'" error
  • Import or require statements for directory paths fail
  • Build process fails when bundling modules that import directories
  • Error stack trace points to a require() or import statement targeting a directory
  • Module resolution works locally but fails in production or CI/CD environments
  • Error occurs after restructuring project directories or renaming files

Common causes

  1. The directory being imported does not contain an index.js file
  2. package.json exists in the directory but the "main" field points to a non-existent file
  3. The index.js file was renamed, moved, or deleted without updating imports
  4. File casing mismatch between import statement and actual filename (case-sensitive filesystems)
  5. The "exports" field in package.json overrides default resolution without including the directory path
  6. Build tools or bundlers generated incorrect output directory structure
  7. Git ignored the index.js file, causing it to be missing in deployment environments
  8. Dependencies were not properly installed, resulting in incomplete node_modules directories

How to fix "Error: Cannot find module './index'"

1Verify the directory structure and locate the missing index.js file

First, check if the directory being imported actually contains an index.js file:

bash
# Navigate to the directory being imported
ls -la ./path/to/directory

# Check if index.js exists
test -f ./path/to/directory/index.js && echo "File exists" || echo "File missing"

If the file is missing, you need to either create it or update your import to point to the correct file.

2Create the missing index.js file if needed

If the directory should export a module but lacks an index.js file, create one:

javascript
// path/to/directory/index.js
// Export the main functionality from this directory
module.exports = require('./main-file');

// Or for ES modules:
export { default } from './main-file.js';
export * from './other-exports.js';

This creates a proper entry point that Node.js can resolve when importing the directory.

3Check and fix package.json main field if present

If a package.json file exists in the directory, verify the "main" field:

json
{
  "name": "my-module",
  "main": "index.js",
  "type": "commonjs"
}

Ensure the path in "main" is relative to the package.json location and the file actually exists. Common mistakes:

json
// ❌ Wrong - absolute path
{ "main": "/src/index.js" }

// ❌ Wrong - file doesn't exist
{ "main": "dist/index.js" }

// ✅ Correct - relative path to existing file
{ "main": "./index.js" }
4Update import statements to reference specific files

Instead of importing directories, explicitly import the specific file:

javascript
// ❌ Directory import (requires index.js)
const myModule = require('./utils');

// ✅ Explicit file import
const myModule = require('./utils/helpers.js');

// For ES modules, always include the extension:
import myModule from './utils/helpers.js';

This approach is more explicit and avoids relying on implicit index file resolution.

5Verify file casing matches import statements

Check that file names match exactly, including case:

bash
# Find files with case-insensitive search
find . -iname "index.js"

# This might reveal Index.js or INDEX.js instead of index.js

Fix any casing mismatches:

bash
# Rename to lowercase (Git-aware)
git mv Index.js index.js

Remember: macOS and Windows are case-insensitive by default, but Linux servers are case-sensitive.

6Reinstall dependencies if the error involves node_modules

If the missing module is in node_modules, reinstall dependencies:

bash
# Remove existing installations
rm -rf node_modules package-lock.json

# Reinstall all dependencies
npm install

# Or with yarn
rm -rf node_modules yarn.lock
yarn install

This ensures all packages are properly installed with their correct directory structures.

7Check .gitignore and ensure index.js is tracked

Verify that index.js isn't being ignored by Git:

bash
# Check if file is ignored
git check-ignore -v path/to/directory/index.js

# View what files are tracked
git ls-files path/to/directory/

If the file is incorrectly ignored, update your .gitignore:

gitignore
# Make sure you're not ignoring index files
# ❌ Too broad
*.js

# ✅ More specific
dist/**/*.js
build/**/*.js

Then track the file:

bash
git add -f path/to/directory/index.js
git commit -m "Add missing index.js file"

Advanced notes

ES Modules vs CommonJS: When using ES modules (with "type": "module" in package.json), you must include file extensions in all import statements, even for index.js files. The implicit index file resolution still works, but you need to reference it as './directory/index.js' explicitly or use the directory path './directory' (which will resolve to index.js).

Exports Field Precedence: In modern Node.js packages, the "exports" field in package.json takes precedence over "main". If a package defines "exports" without including a mapping for the directory path you're importing, the import will fail even if index.js exists. Check the package's exports configuration:

json
{
  "exports": {
    ".": "./index.js",
    "./utils": "./src/utils/index.js"
  }
}

Circular Dependencies: Sometimes this error appears when refactoring code with circular dependencies. If module A imports directory B, which contains an index.js that imports module A, Node.js may fail to resolve the index.js file during the circular resolution. Use tools like madge to detect circular dependencies:

bash
npx madge --circular --extensions js ./src

Bundler Considerations: Build tools like webpack, Rollup, or esbuild have their own module resolution algorithms. If your code works in development but fails in production builds, check your bundler's configuration for directory import handling and ensure output paths match expected structures.

Monorepo and Workspace Issues: In monorepos using npm workspaces, Yarn workspaces, or pnpm, symlinked packages may have missing index.js files if workspace dependencies aren't properly linked. Run npm install or yarn install at the workspace root to ensure all internal dependencies are correctly symlinked.

Frequently asked questions

What does "MODULE_NOT_FOUND" mean?
js's module resolution system attempted to load a directory as a module but failed to find the expected entry file. node files in that directory. js cannot determine how to load the module and throws this error.
How do I fix "MODULE_NOT_FOUND"?
This error occurs when Node.js attempts to import a directory but cannot locate an index.js file or a valid entry point specified in package.json. It typically happens when directory imports rely on implicit index file resolution.
What causes "MODULE_NOT_FOUND"?
The directory being imported does not contain an index.js file package.json exists in the directory but the "main" field points to a non-existent file The index.js file was renamed, moved, or deleted without updating imports
Is the "MODULE_NOT_FOUND" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading