Using Multiple Front End Package Managers Simultaneously (Bower, NuGet)

Question

The (unofficial) convention for writing NuGet packages for front-end libraries seems to be to strip out the JavaScript files and put them in the Scripts folder, and strip out the CSS files and put them in the Content folder. Rarely are these files put in subfolders, so you end up with a huge number of files littering the Scripts and Content folders.

The only way to separate your own code is to put that in a subfolder, or a different folder altogether (see the SPA templates Durandal and HotTowel where an "App" folder is added).

I personally like the "unopinionated" solution that Twitter Bower provides. Put all front-end packages in a root folder called "Components" and do not mess with the original structure of the package.

I am wondering about giving up on NuGet for front-end libraries and using Bower instead and just wonder if anyone has any experience of combining the two? Alternatively, is there a way to install GitHub repos directly using NuGet without creating a NuGet package?

Answer 1

We use NuGet and Bower both and it has worked well for us so far. We are slowly moving the front-end libraries to Bower. You will have to create a Nuget package to use it from Nuget to install.