Node's nested node_modules approach is basically incompatible with Windows
1–10 of 62 posts
Re: Node's nested node_modules approach is basically incompatible with Windows
#2This looks like a Docker container on Digital Ocean.
I would use this a lot, but many errors trying to apt-get install packages.
Re: Node's nested node_modules approach is basically incompatible with Windows
#3[deleted]
Re: Node's nested node_modules approach is basically incompatible with Windows
#4Was the recursive "every package include its dependencies" done just because it was easier? Or was it a conscious design choice.
Re: Node's nested node_modules approach is basically incompatible with Windows
#5Was the recursive "every package include its dependencies" done just because it was easier? Or was it a conscious design choice.
Well at least there is no possibility of conflicts(unlike some other pm). The problem is people writing modules that have like 1 function while requiring 10 other modules that have just 1 function themself that require 10*10 other modules ... Of course it doesnt scale,and of course the package manager wont scale either...
But it's not a NodeJS problem it is a NPM problem.NodeJS has other problems though(the lack of governance by a dedicated foundation is the most important one,the obvious second one is nodejs dependency on what google does/doesnt do,since google maintains V8).
Re: Node's nested node_modules approach is basically incompatible with Windows
#6The title looks exaggerated. I thought NodeJS cannot just run on Windows anymore. It's not the case though, it does - it's just it creates folders that are nested.
Re: Node's nested node_modules approach is basically incompatible with Windows
#7Was the recursive "every package include its dependencies" done just because it was easier? Or was it a conscious design choice.
Personally, I consider the way Node does module loading one of its best features. No need to worry about version conflicts, because every module can (optionally) pull in a specific version if necessary. And no need to worry about constructing some ridiculous environment variable, because of the implicit relative pathing.
I've been writing Python and Go for the last 12 months, and by comparison their module systems are absolute disasters.
Re: Node's nested node_modules approach is basically incompatible with Windows
#8This definitely seems more like a Windows issue than a Node issue.
Re: Node's nested node_modules approach is basically incompatible with Windows
#9[deleted]
Re: Node's nested node_modules approach is basically incompatible with Windows
#10What percent of the node.js community will this effect?
What's the design reason for Windows tools to only have a max of 260 file path chars? If it's not the OS, but the tools he is using, why not use tools that work? Isn't this the tools bug?
Honestly, if he is doing web development, his life will be easier with a linux distro.