Could not read from file: light\node_modules\node-stdlib-browser\esm\mock\empty.js\promises about vite-plugin-node-polyfills HOT 6 CLOSED

I think adding support for subpath matching should solve this issue. It's now on my todo list.

from vite-plugin-node-polyfills.

I've got the same problem.

from vite-plugin-node-polyfills.

Could either of you provide a minimal reproduction using StackBlitz or a similar service?

from vite-plugin-node-polyfills.

Hi - I encountered a similar issue which I have recreated
Here on stacklitz.

npm run dev or npm run build to see the error.

[vite-plugin-sveltekit-compile] Could not load /home/projects/vitejs-vite-wp5msv/node_modules/node-stdlib-browser/esm/mock/empty.js/promises (imported by node_modules/path-scurry/dist/mjs/index.js): ENOTDIR: not a directory, open '/home/projects/vitejs-vite-wp5msv/node_modules/node-stdlib-browser/esm/mock/empty.js/promises'
✓ built in 3.51s
error during build:
ENOTDIR: not a directory, open '/home/projects/vitejs-vite-wp5msv/node_modules/node-stdlib-browser/esm/mock/empty.js/promises'```

from vite-plugin-node-polyfills.

same issue when useing webdriverio, or puppeteer packages (web driver automation libraries)

just import them
import {remote} from 'webdriverio'

and these are places that vite stuck:

node_modules/webdriverio/build/utils/index.js:1:15:
1 │ import fs from 'node:fs/promises';

node_modules/fetch-blob/streams.cjs:14:40:
14 │ Object.assign(globalThis, require('node:stream/web'))

from vite-plugin-node-polyfills.

After looking into this more, I think the best solution is to either use the new overrides feature (which would allow you to use your own polyfill for fs) or to externalize the dependency using something like vite-plugin-externalize-deps.

from vite-plugin-node-polyfills.