Skip to main content

How to Resolve "Error: Cannot find module 'node-sass'" Error in JavaScript

The Error: Cannot find module 'node-sass' is a common and often frustrating issue in front-end development. It typically occurs during a build process (e.g., with Webpack) and signifies a problem with your Sass compilation setup. This error is more complex than a typical "module not found" error because node-sass has a native C++ binding that must be compatible with your Node.js version.

This guide will first explain the root cause and the modern, recommended solution, which is to migrate away from the deprecated node-sass package. It will then cover the legacy solutions for projects that must still use node-sass, including how to fix version incompatibilities and perform a clean reinstall.

Understanding the Root Cause: node-sass and its C++ Binding​

The node-sass package is a Node.js binding for LibSass, a C++ library that compiles Sass. This means it's not a pure JavaScript package. When you install node-sass, it needs to download or build a binary file that is specific to your operating system and your exact version of Node.js.

The Error: Cannot find module 'node-sass' error occurs for two main reasons:

  1. It's not installed: The package is missing from your node_modules folder.
  2. Version Mismatch: The installed version of node-sass is incompatible with your version of Node.js, and the correct binary could not be built or downloaded.
note

Important: The node-sass package is deprecated. The official and modern replacement is the sass package, which is a pure JavaScript implementation and does not have these complex dependency issues.

For any new project, or if you are able to update an existing one, the best long-term solution is to stop using node-sass and switch to sass (also known as Dart Sass). It is faster, more reliable, and has no complex native bindings.

The logic:

  1. Uninstall the old node-sass package.
  2. Install the new sass package. Most modern build tools (like Webpack with sass-loader) will automatically detect and use sass if it's available.

Solution:

# 1. Uninstall the old package
npm uninstall node-sass

# 2. Install the new 'sass' package as a development dependency
npm install --save-dev sass

For most projects, this is the only change you need to make. After running this, delete your node_modules folder and reinstall to ensure a clean state.

Legacy Solutions (If You Must Use node-sass)​

If your project is older or has dependencies that require you to continue using node-sass, use these troubleshooting steps.

Fix Version Incompatibility Between node-sass and Node.js​

This is the most common node-sass-specific problem.

A possible problem is when you have a version of Node.js that is too new or too old for the node-sass version specified in your package.json.

The Solution

  1. Check your Node.js version. 
    node -v
    // Output: v18.12.1
  2. Check the official node-sass compatibility table. Find your Node.js version to see which node-sass version you need.
Node.js VersionSupported node-sass Version
Node 18+8.0+
Node 166.0+
Node 144.14+
Node 124.12+
  1. Install a compatible version. If your Node.js version is 18, but your project is trying to install node-sass@4.12.0, it will fail. You must install a compatible version. 
    # Install a specific, compatible version
    npm install --save-dev node-sass@8.0.0

Install the Missing node-sass Package​

If the package is simply missing from your package.json, install it as a development dependency.

npm install --save-dev node-sass

Perform a Clean Reinstall of Dependencies​

A corrupted node_modules folder or package-lock.json file can cause stubborn issues. A full, clean reinstall often fixes these.

The solution is to run the following commands from your project's root directory.

For macOS / Linux:

rm -rf node_modules
rm -f package-lock.json yarn.lock
npm cache clean --force
npm install

For Windows (CMD):

rd /s /q "node_modules"
del package-lock.json
del yarn.lock
npm cache clean --force
npm install

After reinstalling, restart your code editor and development server.

Conclusion​

The Error: Cannot find module 'node-sass' error is a clear signal of a dependency problem, often complicated by the native bindings of the node-sass package.

To fix it:

  • The best and recommended long-term solution is to migrate from node-sass to sass. This avoids the underlying compatibility issues entirely.
  • If you must use node-sass, the most likely cause of the error is a version mismatch between node-sass and your installed version of Node.js. Check the compatibility table and install a compatible version.
  • If all else fails, a clean reinstall of all your node_modules will resolve any corruption or inconsistency in your dependencies.

Table of Contents