@tilgovi Sounds like we're on the same wavelength. Admittedly, a lot of npm modules simply won't work in the browser. But a lot of them would. And admittedly, some will only work if the exact versions of the dependencies declared in package.json are used, rather than simply using the latest version. But a lot of them would. And some are going to be dependent on Node's internal module cache architecture and side effects and not work with shims for the builtins. But that's the exception. A LOT of them though are going to rely on package.json's "module", "browser", or "main" property, the default "index.js" assumption, and the directory ascending algorithm. That's a major hurdle, but one that can be overcome with lots of calls to window.fetch. Once resolved though we can cache the results so it's faster on the next page reload.