Skip to content


Switch branches/tags

Microsoft + Node.js Guidelines

Microsoft ❤️ Node.js!

We work hard to contribute to the Node.js community and we want to make sure your experience is as seamless as possible. In particular, our goals here are to:

  • make it easier for people using Microsoft services and technologies to get started on the right foot with Node.js
  • consolidate Microsoft's Node.js offerings in a centralized place to make it easier for you to find information
  • communicate status on key issues we're addressing and collect feedback from the Node.js community on how we can do better.
  • provide a forum to connect with various teams at Microsoft working on improving the Node.js experience.

Note that this is not intended to be a comprehensive set of recommendations. Rather it's meant to be a helpful set of content that makes it easier to avoid any potential gotchas, and the beginning of what we expect to be an ongoing conversation on how we can improve the Node.js experience on Microsoft platforms.

Emoji legend

💡 This is a tip that provides the reader with some additional info that's not necessary, but potentially useful for the task at hand.

🚩 TODO This describes a todo item that we'd like some help with.

📈 IN PROGRESS This provides awareness about an important issue that we're currently working on resolving.

Getting Started with Node.js

Node.js + Microsoft products, services, and contributions

🚩 TODO Add other Microsoft services related to Node.js.

General Node.js tips, tricks, resources, and more!

Contributions Welcome!

This is still a work in progress, an experiment - if you will, and we'd love your help to make it better! Please see our contributing guidelines for details.


Tips, tricks, and resources for working with Node.js, and the start of an ongoing conversation on how we can improve the Node.js experience on Microsoft platforms.


Code of conduct





No releases published


No packages published