I work in a team that's predominately ASP.NET MVC when it comes to web development. We're merging with another government agency 's development and they're using Node.js.

So I figure that I should make an effort and learn Node.js as I've only had minimal exposure to it.

After five minutes discover that corporate proxy prevents access to npm. Oh well, never mind!

@jAsE In what terms exactly?

@jAsE I don't disagree. Just thought it would help collaboration if I understood their applications better.

Wasn't suggesting that we should switch to Node.js as we have several complex applications dependent on multithreading and intense CPU usage that I don't think would be suitable. But always good to have other options as there may be some smaller projects where Node.js is the better option.

I guess I'll add this to my list of things that are unnecessarily restrictive in our infrastructure.

@jAsE yep sure. Not being able to access npm prevents us from using it at work for now. But doesn't stop me learning it in my own free time.

Maybe they have their own enterprise npm registry