(Better) Node.js builtin emulation for client-side JS

Describe the problem

I've found many NPM packages that almost work in SvelteKit client-side JS, but their access to node builtins like process and buffer results in errors. For example:

• ReferenceError: process is not defined (json-schema-to-zod)
• ReferenceError: process is not defined (google-photos-album-image-url-fetch)
• Module "path" has been externalized for browser compatibility. Cannot access "path.extname" in client code. (gphotos-scraper)

There is a work-around for these errors, but it's neither obvious nor simple:

• Fix for local dev errors.
• Fix for build-time errors

Most average Svelte devs may just assume it's not possible (like I did at first).

Describe the proposed solution

Ideally SvelteKit would provide something similar to Parcel's Polyfilling & Excluding Builtin Node Modules

The SvelteKit DX would be greatly enhanced by integrating the work-arounds linked above as either default or optional configurations.

If the work-arounds are not included (by default), detecting this class of error and giving meaningful error messages pointing to the correct work-arounds would still be very helpful.

Alternatives considered

• It is possible to use the work-arounds linked above.
• Limiting use of the problem modules to server-side JS, and wrapping with internal endpoints.

Importance

would make my life easier

Additional Information

Simple repro demonstrating problem:

• https://kit-bugs-git-node-builtins-bug-leftium.vercel.app/
• https://github.com/Leftium/kit-bugs/tree/node-builtins-bug

Start with the linked minimal reproduction and its node-builtins-bug branch, then review the reported process, buffer, and path failures alongside the linked Vite and Parcel guidance. Done would require an agreed SvelteKit approach for client-side Node builtin emulation, or actionable diagnostics that direct users to supported workarounds.