On Sun, Sep 18, 2022 at 8:48 AM Floh <[email protected]> wrote: > > ...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. >
*nod* that's sensible enough -- node has felt stabler than python during the 2/3 switch, but node isn't free of back-compat problems too. :) I'd be fine with bundling it for internal usage, as long as it's out of the PATH. -- 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/CAFnWYTnHh1%2BTFZ5v3uwEzTSrxFqAZ1ZH%3DO3arfQce9CWNkOC4Q%40mail.gmail.com.
