Yeah there will be plenty off issues using npm. The native npm packages will most likely break. Npm has support for binary builds but I'm not sure most packages will have a completely separate build process set up for windows.<p>In the case of the mongodb package I'm deprecating the c++ bson parser as the js parser is as fast or faster than the c++ bson parser (v8 crankshaft and fast arrays rock) and this "should" make it work out of the box on the windows node.js build (crossing fingers)
That was quick! Wasn't this just announced in June?<p><a href="http://blog.nodejs.org/2011/06/23/porting-node-to-windows-with-microsoft%E2%80%99s-help/" rel="nofollow">http://blog.nodejs.org/2011/06/23/porting-node-to-windows-wi...</a>
Unless you are deploying on Windows, why not run it under cygwin? You may end up with a lot of silly problems with file paths, case insensitivity and any other "impedance mismatch" between your development environment and whatever server the workload will run on.<p>I did a lot of Django development on Windows and Cygwin saved me a whole lot of pain.
Just throwing it out there, but what is the real reason behind making it windows friendly? Do developers want it or is it done with intentions to make it more appealing for corporate absorption?