Ouch, this is annoying indeed :/ Changing emsdk to install to a shorter path could only optimize out that "emsdk/node/4.1.1_64bit/bin" part of the path. Whatever comes before is dictated by where you cloned emsdk to, and whatever comes afterwards is dictated by Node.js itself. I doubt that shortening such a small part of the path would help much. I'd recommend posting this bug query to upstream Node.js bug tracker, it sounds like with such long npm install path chains, they should definitely have seen the issue already before.
2017-02-08 22:55 GMT+02:00 Dan East <[email protected]>: > I've checked my Emscripten SDK into Mercurial on Windows. The SDK is > pulled onto developer and build machines. On some machines, based on the > target path length, a certain node_modules path is too long: > > node/4.1.1_64bit/bin/node_modules/npm/node_modules/ > request/node_modules/har-validator/node_modules/is-my- > json-valid/node_modules/generate-object-property/node_modules/is-property > > Is there a way to shorten that path or change the "emsdk install latest" > command so that it uses a shorter path? I noticed Emscripten is using Node > 4.1.1. Is the node_modules path length problem fixed in a later release? > > Thanks, > Dan > > -- > 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]. > For more options, visit https://groups.google.com/d/optout. > -- 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]. For more options, visit https://groups.google.com/d/optout.
