| You seem very angry and I clearly don't understand what you are talking about. > And you're not really responding to the substance of the comment anyway, which is that JS programmers—frequently writing for browser runtimes, even—are demanding that you install NodeJS, Bun, or Deno (because they hardcode the build scripts against those runtimes' APIs). Do you mean things like the Typescript + Webpack/whatever toolchain? Because broadly speaking that seems orthogonal to the target browser. Using tools outside the browser to build something for the browser is mostly an optimization, for both the developer and the end user. If someone has a web app with maybe 100 NPM packages, doing things like tree-shaking offline before shipping to a browser is important. > And you're not really responding to the substance of the comment anyway, which is that JS programmers—frequently writing for browser runtimes, even—are demanding that you install NodeJS, Bun, or Deno (because they hardcode the build scripts against those runtimes' APIs). If they are targeting Web APIs and using runtimes to build for those APIs what is the problem? There are plenty of tools that need version X.XX+ of GCC to build and won't build using MSVC or something. It's a bit annoying but hardly outrageous. |
Luckily you managed to frame it so that the failure comes across like something that I got wrong and messed up and am responsible for, and that's the most important thing.