VITE: get rid of externalized "node:xyz" warnings on build

[akomm]

I gave the migration to VITE another shot and now my older project runs fine both in dev and prod. I have though one issue:

I try to avoid having tons of warnings and ignore them in my builds. And one annoying is the vite resolve plugin externalizing all the node:xyz usages. Mostly from within the unidici pollyfills, some from remix packages.

Is there any way to resolve this in a clean way, without muting the error/warning channel, so I can see real issues?

[akomm]

After a second thought, that might be a trace that some server code has been leaked into client? I use a lot .server file / folder and I've tried to figure out if any library server code ends up in client bundle with the vite visualize plugin, but did not find any of the packages that generate a warning in it. Might also be "hidden" by obfuscating of the chunk names. So far I don't find a reliable way to figure out unintended inclusion in the client. Tried to follow the trail of unidici and remix code to my code, but there is nothing pointing to any of my files (build/client either).

The usage from this files:

@remix-run/node/dist/sessions/fileStorage.js
@remix-run/node/dist/upload/fileUploadHandler.js
@remix-run/node/dist/stream.js
undici/index.js
stream-slice/index.js
undici/lib/dispatcher/client.js
undici/lib/dispatcher/dispatcher.js
undici/lib/dispatcher/proxy-agent.js
undici/lib/core/util.js
undici/lib/mock/mock-client.js
undici/lib/mock/mock-pool.js
undici/lib/handler/retry-handler.js
undici/lib/core/connect.js
undici/lib/handler/redirect-handler.js
undici/lib/web/fetch/response.js
undici/lib/web/fetch/request.js
undici/lib/web/fetch/formdata.js
undici/lib/web/fetch/index.js
undici/lib/web/websocket/events.js
undici/lib/web/fetch/data-url.js
undici/lib/web/eventsource/eventsource.js
undici/lib/web/websocket/websocket.js
cookie-signature/index.js
undici/lib/core/diagnostics.js
undici/lib/core/request.js
undici/lib/dispatcher/client-h2.js
undici/lib/api/api-request.js
undici/lib/api/api-stream.js
undici/lib/api/api-pipeline.js
undici/lib/api/api-upgrade.js
undici/lib/api/api-connect.js
undici/lib/mock/mock-utils.js
undici/lib/dispatcher/client-h1.js
undici/lib/mock/pending-interceptors-formatter.js
undici/lib/dispatcher/client-h1.js
undici/lib/mock/pending-interceptors-formatter.js
undici/lib/web/fetch/body.js
undici/lib/web/fetch/util.js
undici/lib/web/fetch/webidl.js
undici/lib/web/fetch/file.js
undici/lib/web/fileapi/util.js
undici/lib/web/cookies/parse.js
undici/lib/web/cookies/util.js
undici/lib/web/cache/cache.js
undici/lib/web/eventsource/eventsource-stream.js
undici/lib/web/websocket/util.js
undici/lib/web/websocket/connection.js
undici/lib/web/websocket/frame.js
undici/lib/web/websocket/receiver.js
undici/lib/api/readable.js
undici/lib/api/util.js
undici/lib/web/fetch/formdata-parser.js
undici/lib/llhttp/llhttp_simd-wasm.js
undici/lib/llhttp/llhttp-wasm.js
undici/lib/web/cache/util.js

[akomm]

By the way, the issue went away after some refactoring and optimizing of imports, but I did not know why exactly. Now I think I know, and its one of the things I've corrected.

This is the reason for the warnings:
#8949