Hi Mike Full disclosure, I work on a team at Microsoft whose sole mission is to make Node work well on Windows and Windows Azure.
There are *not* a ton of modules that fail. The majority actually work just fine. With node-gyp becoming the defacto standard for native modules, most work just as well, though you have to install python and VS C++ express on the box to build native modules. There are still some native modules that have not upgraded and use node-waf which does not work on Windows. The node core team (which includes contributors from Microsoft) have worked very hard to make a proper story for node on Windows. Recently Microsoft Open Tech did a bunch of work to advance Windows support by adding<http://blogs.msdn.com/b/interoperability/archive/2012/12/03/ms-open-tech-contributes-support-for-windows-etw-and-perf-counters-to-node-js.aspx>ETW, Performance Counters and flamegraph support. I think we've closed a lot of the gaps. We have some very large organizations both externally and internally with large deployments (thousands of servers) running on node on Windows. Not to say that there is not more work we can do. My personal mission right now is to improve our native module story as it is still painful to have to have all the dev tools installed. On Wed, Nov 28, 2012 at 12:25 AM, Rakshit Menpara <[email protected]>wrote: > Never used windows for deployment, but we did have a few problems > onboarding new devs on windows a while back. Our application is using > express, mongoose (node-mongodb-native), socket.io and redis among many > other modules. All but bcrypt worked fine on windows - it didn't compile. > But, it seems that the issue is resolved now ( > https://github.com/ncb000gt/node.bcrypt.js/pull/92). > > Hope it helps. > > -- > Rakshit Menpara > > On Wednesday 28 November 2012 at 11:39 AM, Mike Nichols wrote: > > I've been in nodejs for the last year and one project just asserted > deployment will be on Windows instead of Linux. > > Specifically, this could sit on a Windows 7 Professional machine (64-bit). > Cloud deployment isn't an option. > > I have been scouring the web for folks' experiences with deploying nodejs > apps on Windows and saw this nice writeup (https://gist.github.com/2790533) > which gave me some confidence. > > My nodejs app will likely use ExpressJS but could port to my own cobble > resembling the www-npm project. Are there a ton of npm modules out there > which fail on Windows or are people confidently deploying node apps on > Windows? > > Any experience with nodejs on Windows in the wild would be very helpful. > > Before gouging my eyes out because of reverting into .Net app-land I'd > like to be sure it is necessary to do so :) > > Thanks! > Mike > > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
