Here's a fresh episode of MyGet's NuGet and NPM news from the community! Like each month, we'll look at some interesting blog posts and articles found on the Internet, curated by our MyGet founders Xavier and Maarten. Follow @MyGetTeam on Twitter for more!
Let's start with the big one: Visual Studio 2017 has been released. A new IDE with a revamped project system (bye
project.json), .NET Core tooling and more. Oh, and a fresh NuGet.exe 4.0.
Sean Feldman shares a great blog post about leveraging MyGet web hooks and Azure Functions for sending out notifications.
In VSIX Continuous Delivery using Cake, AppVeyor and MyGet (do make sure to read the entire series), Alistair Chapman covers setting up a CI/CD pipeline using best-of-breed tools.
Steve Desmond released a new tool called LibYear. It is an addon to
dotnet.exe and scans a project for outdated package references. It also features an
update command to update all referenced dependencies in one go.
NuGet Package Explorer is now a Windows Store application.
Just like ReSharper has been doing since forever, Visual Studio 2017 now suggests installing NuGet packages for missing types.
The .NET Core folks started an announcement repository to which you can subscribe to be notified of announcements and changes in .NET Core.
Matt Warren wrote a post with pointers to the .NET Core internals source code. Great list of resources if you want to dive deep into the new .NET.
Ivan Gavryliuk posted NuGet Versioning Hell. Not a rant, but a post on the importance of proper versioning.
In the 4.3 branch, NPM released v4.3.3. A fresh NPM version v4.4.1 has landed! Nothing special though, just making sure all NodeJS versions are supported. There is also v4.4.2, bringing along a number of bugfixes. And v4.4.3. And v4.4.4. Or maybe just install the latest v4.5.0.
NPM has an RFC open related to file type dependency specifiers. It makes depending on files inside of our
package.json 's dependencies easier. It can point to a package on disk, either compressed or extracted.
Nihar Sawant wrote a post on developing an interactive command line application using Node.He uses the
commander package to build a sample application, which is pretty nifty and handles the async and promises nature of Node in an easy to read manner.