With our latest MyGet release, we’ve added support for npm and bower registries. We’ve always been very focused on building a great story around NuGet and decided it was time for Npm and Bower enthusiasts to get a similar experience.
Adding npm and Bower support was high on our wish list and that of our users. Many developers are doing only front-end development and need a public or private npm registry. Others are working with DNX (the new name for ASP.NET 5 or ASP.NET vNext) and combine NuGet, npm and Bower. It feels good to be able to support them all!
To help you get started, we’ve prepared a few short tutorials that help you get started on MyGet with these package managers:
Oh and build services now also packages node modules! Just point MyGet to your GitHub repository and we’ll package your npm packages, too.
We really look forward to hearing your feedback on this!
MyGet 2.0 was released on March 12, 2015.
This 2.0 release of MyGet adds brand new functionality to the service. With this release, we bring all the functionality we already had for NuGet also to Bower and NPM!
This means, from now on, you can use MyGet to host and build your own NuGet, NPM or Bower feeds, whether public or secured.
MyGet (all plans)
The following applies to all MyGet plans:
MyGet (paid plans)
Obviously all paid plans also get the enhancements made available on the free plan. The following applies to the MyGet Starter and Professional plans:
The enterprise plan has all functionality from the paid subscription plans, and more! The following applies only to the MyGet Enterprise plan:
MyGet Build Services
- Improved detection of hanging builds
- Build now properly fails when compilation fails and no packages have been produced or pushed to your feed
- Upstream package source proxying enhancements
- No longer prompt the user that a package update is available upstream if the package source is set to auto-update
Keep that feedback coming! MyGet is built for you!