Package Management is generally available: NuGet, npm, and more

Today, I’m proud to announce that Package Management is generally available for Team Services and TFS 2017! If you haven’t already, install it from the Visual Studio Marketplace.

Best-in-class support for NuGet 3

NuGet support in Package Management enables continuous delivery workflows by hosting your packages and making them available to your team, your builds, and your releases. With best-in-class support for the latest NuGet 3.x clients, Package Management is an easy addition to your .NET ecosystem. If you’re still hosting a private copy of NuGet.Server or putting your packages on a file share, Package Management can remove that burden and even help you migrate.

To get started with NuGet in Package Management, check out the docs.

npm in Package Management

Package Management was never just about NuGet. Accordingly, the team has been hard at work over the last few months adding support for npm packages. If you’re a developer working with node.js, JavaScript, or any of its variants, you can now use Team Services to host private npm packages right alongside your NuGet packages.

npm is available to every Team Services user with a Package Management license. To enable it, simply install Package Management from the Marketplace, if you haven’t already, then check out the get started docs.

npm support will also be available in TFS 2017 Update 1. Keep an eye on the features timeline for the latest updates.

npm in Package Management

GA updates: pricing, regions, and more

If you’ve been using Package Management during the preview period, you’ll now need to purchase a license in the Marketplace to continue using it. Your account has automatically been converted to a 60-day trial to allow ample time to do so. Look for the notice bar in the Package Management hub or go directly to the Users hub in your account to buy licenses.

The pricing for Package Management is:

  • First 5 users: Free (but licenses for these users must still be acquired through the Marketplace)
  • Users 6 through 100: $4 each
  • Users 101 through 1000: $1.50 each
  • Users 1001 and above: $0.50 each

The Package Management extension is also included with these Visual Studio subscriptions:

  • Visual Studio Enterprise – monthly
  • Visual Studio Enterprise – annual
  • Visual Studio Enterprise with MSDN

See our pricing calculator for further information. Only Visual Studio Team Services users (not stakeholders) can be assigned the Package Management extension.

Finally, Package Management is now also available in the India South and Brazil South regions.

What’s next?

With the launch of Package Management in TFS 2017, the team is now fully focused on adding additional value to the extension. Over the next year, we’ll be investing in a few key areas:

  • Package lifecycle: we want Package Management to serve not just as a repository for bits, but also as a service that helps you manage the production and release of your components. Accordingly, we’ll continue to invest in features that more closely integrate packages with Team Build and with Release Management, including more investments in versioning and more metadata about how your packages were produced.
  • Dependency management: packages come from everywhere: NuGet.org, teams across your enterprise, and teams in your group. In a world where there’s always pressure to release faster and innovate more, it makes sense to re-use as much code as possible. To enable that re-use, we’ll invest in tooling that helps you understand where your dependencies are coming from, how they’re licensed, if they’re secure, and more.
  • Refreshed experience: when we launched Package Management last November, we shipped a simple UX that worked well for the few scenarios we supported. However, as we expand the service with these new investments, we’ll be transitioning to an expanded UX that more closely matches the rest of Team Services, provides canvases for partners to extend Package Management with their own data and functionality, and gives us room to grow.
  • Maven/Ivy: as the rest of the product builds ever-better support for the Java ecosystem, it follows that Package Management should serve as a repository for the packages Java developers use most. So, we’ll be building support for Maven packages into Package Management feeds.