Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

Node.js or the bundler cannot resolve fs/promises

ErrorError: Cannot find module 'fs/promises'

Short answer

The fs/promises import path exists only in Node.js 14 and later, and only in code that runs on Node.js. Either your Node.js is older than 14, or a bundler is compiling Node-only code into a browser build. Upgrade Node.js, or keep the fs code out of the browser bundle.

  • Applies to Node.js 22, Node.js 24, webpack 5
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Check which Node.js version actually runs the command. It is often not the one you expect.

    node --version
    which node
  2. 2Match what you see, then jump to its fix

    1. 1Error: Cannot find module 'fs/promises' when you run node, with node --version below v14Node.js is older than 14Fix
    2. 2Module not found: Error: Can't resolve 'fs/promises' during an Angular, Vue or Nuxt buildNode-only code is being bundled for the browserFix

What does the error look like?

  • Error: Cannot find module 'fs/promises'
  • Module not found: Error: Can't resolve 'fs/promises'

Cause 1 of 2

Node.js is older than 14

1Check

The fs/promises path was added in Node.js 14.0.0. Before that, the same API lived only at require('fs').promises.

node -e "console.log(process.version)"

2Fix

Install a current LTS release of Node.js. If you cannot upgrade yet, read the API from fs instead.

// works on old and new Node.js
const { readFile } = require('fs').promises;
// current form
const { readFile: read } = require('node:fs/promises');

3Verify

Run the script again.

node app.js

Confirmed by nodejs.org

Did this fix it?

Cause 2 of 2

Node-only code is being bundled for the browser

1Check

A browser build has no fs module. Webpack 5 no longer supplies stand-ins for Node core modules, so an import that reaches a client bundle fails to resolve. Find which file imports it.

grep -rn "fs/promises" src/

2Fix

Move the file reading to server code (an API route, a build script or SSR-only module) and send the data to the browser. If a dependency imports it but never calls it in the browser, tell webpack to leave it out.

// webpack.config.js
module.exports = {
  resolve: {
    fallback: { 'fs/promises': false },
  },
};

3Verify

Rebuild; the unresolved-module error is gone.

npm run build

Confirmed by webpack.js.org

Did this fix it?

How do I stop it coming back?

  • Pin the Node.js version in the project so every machine and CI runner uses the same one.
  • Import Node built-ins with the node: prefix so it is obvious which code is server-only.
  • Keep file-system code in modules that browser code never imports.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

ng serve says it cannot determine the project or target

Cannot determine project for command.

The Angular CLI looked through angular.json for a project that defines the target you asked for (serve, build, test) and found none, or found several and could not pick one.

3 causes, each with a fix

Back end

ng serve cannot find the dev-server builder package

Could not find the implementation for builder @angular/build:dev-server

The builder named in angular.json (for example @angular-devkit/build-angular:dev-server) is looked up as an npm package starting from the workspace root.

3 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.