I've worked with nodejs on Windows daily for years now and have very few issues. Almost all of those issues can be related to: - Bad npm scripts in `package.j

I've worked with nodejs on Windows daily for years now and have very few issues. Almost all of those issues can be related to: - Bad npm scripts in `package.json`; usually maintainers with a severe OS X slant who don't consider that setting environment variables requires some cross-platform love (getting better though thanks to an awareness of this in the community and packages handling it such as `cross-env` and `better-npm-run`) - Modules that require being built via node-gyp require some combination of Python 2 and VS 2010. Once these are on your PATH there is no more friction. - Path lengths are not an initial problem with npm 2 on install but will grow to be an annoyance later. The flat(-ter) module folders provided by npm 3 is welcome.