> ...and I would strongly prefer not to have a bundled node at all. Hmm, I have the opposite opinion tbh, Node *should* be bundled, but shouldn't be added to the path (so that the bundled version doesn't collide with any globally installed version), and the Emscripten SDK shouldn't accidentially call any globally installed node version (only the bundled one).
I'd prefer this because at work I'm seeing that projects often depend on older node/npm versions (at least there's nvm to easily switch between versions), but having Emscripten depend on a globally installed node version would only add to the confusion (and probably swamp the Emscripten team with bugs which would actually be node compatibility issues). Same with python2 vs python3. On Saturday, 17 September 2022 at 22:43:49 UTC+2 [email protected] wrote: > On Sat, Sep 17, 2022 at 11:03 AM 'Sam Clegg' via emscripten-discuss < > [email protected]> wrote: > >> >> I'd like to know who many folks are actually using the emsdk version of >> node. For example, do you run tests using this version node? If we >> didn't add it to your PATH by default would that be annoying/confusing for >> you? >> > > I guess I "use" it because when I run "npm" and "node" in my build process > that's what gets run. But I would absolutely never choose it, and I would > strongly prefer not to have a bundled node at all. > > -- brion > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/8f4ed2f0-ba10-4a3f-8d90-b8c4b58fb580n%40googlegroups.com.
