In my case I was using nvm to manage multiple node versions.

During the npm package installation, and throughout development, I used Node v14 but for some reason, my terminal was pointing to Node v12 when I tried bundling my program afterwards.

Switching it back to Node v14 using nvm use 14 solved my issue.

So make sure you're using the correct node version.

In that case i fix the problem in that way: const fs = require('fs').promises;

instead of: const fs = require('fs/promises');

downgrade electron "electron-builder": "^22.10.5", or upgrade nodejs to 14+ v

downgrade to "electron-builder": "~22.10.5" is working for me

I experienced this issue a few days ago as well. I realized that trying to fix another issue, I deleted the node_modules folder and the package-lock.json file, then run the npm install command. This made the build to fail with 'fs/promises'. There are 2 solutions to this issue:

1. Download the latest stable Node version. This should have the 'fs/promises' module and will fix the issue.
2. Delete the node_modules folder and bring back the old package-lock.json file to ensure that the package versions remain the same. Then run the npm install command and the issue should be fixed.