Vite build fails with v7.2.8+ and vite-plugin-node-polyfills

[cmdickson]

First off, I'm not sure if this is an issue with rolldown-vite, vite-plugin-node-polyfills or perhaps something in my Vite configuration, but since it started after upgrading rolldown-vite, I thought I'd start here. I'm looking to find a resolution or, if not, some confirmation as to whether this is a rolldown-vite bug so it can be logged appropriately.

After upgrading rolldown-vite to v7.2.8+, builds started failing with the following errors:

[UNLOADABLE_DEPENDENCY] Error: Could not load node_modules/node-stdlib-browser/node_modules/punycode                                                                                                                                                                                                                      
   ╭─[ node_modules/node-stdlib-browser/esm/proxy/url.js:1:24 ]
   │
 1 │ import require$$0 from 'punycode/';
   │                        ─────┬─────  
   │                             ╰─────── Is a directory (os error 21)
───╯

[UNLOADABLE_DEPENDENCY] Error: Could not load node_modules/string_decoder
     ╭─[ node_modules/readable-stream/lib/_stream_readable.js:158:49 ]
     │
 158 │     if (!StringDecoder) StringDecoder = require('string_decoder/').StringDecoder;
     │                                                 ────────┬────────  
     │                                                         ╰────────── Is a directory (os error 21)
─────╯

Library versions:

• rolldown-vite: 7.2.8+
• vite-plugin-node-polyfills: 0.24.0

The build succeeds after downgrading rolldown-vite to v7.2.7.

Here is a link to a minimal reproduction on Stackblitz: https://stackblitz.com/edit/vitejs-vite-tnkyjpt6
The error message/id are slightly different, but I suspect that is due to the virtual nature of the Stackblitz environment.
To see the errors:

1. Run yarn install
2. Run yarn vite build

I saw this bug related to vite-plugin-node-polyfills, but it does not seem to be related.

Thank you

[cmdickson]

Issue was resolved as part of the bug logged here