Using Libman Providers to Coral Front End Libraries

The first package management system I learned to use was Bower.  It was great for the short love affair we had together, but it stopped being supported and I was weary of learning to use one of its replacements.  Fortunately, I haven’t had to with Libman.  Libman’s (Library Manager) simple JSON approach to bringing front end dependencies has been the easiest for me quickly implement and it has been a great addition to Visual Studio.  I implemented it possibly too quickly, however, and overlooked one powerful configuration setting:  provider.

ASP.NET Core – Easy Transition of Bower to NPM

UPDATE (Oct 16, 2018):  I now rely on Libman for my front end management.  I use its 3 different providers to grab the libraries off of cdnjs, unpkg (supposed to include all npm) and filesystem for local files.  See post:  Using Libman Providers to Coral Front End Libraries

I love me some Bower, even with the shadow looming over it that it’s time is done.  Recently, though, it started to do something weird with just restoring/replacing packages that really began to cause problems with my project (and make for some seriously messy 99* commits).

I can do simple task running, etc but still very much a noob to packaging.

Here was my easy solution for removing Bower and switching over to NPM (and accessing those packages through Views).…