How it works...

Every newly installed package will be placed in the lib folder inside the wwwroot folder. This root folder exposes all the files accessed by HTTP requests. It contains all the static files of the application:

In the wwwroot folder, each dependency has its own folder and in this folder, each has its own .bower.json file. This JSON file describes all the information relevant to the client-side framework.

Opening the .bower.json file located in the lodash folder, we can see a JSON object that contains the name, the main files, version, license, and dependencies, if the package has any:

Global information about Bower packages will be visible in the bower.json file at the root of the application, especially the list of the installed dependencies in our application. We can see the details of this file in the following screenshot:

In the project folder named Dependencies, just under wwwrooot, we can also see the list in the following screenshot:

Before Bower, NuGet was the only package manager for all dependencies. We will now use NuGet for .NET external dependencies and Bower for frontend dependencies (JavaScript, CSS, fonts, and so on). Bower is installed when any version of Visual Studio is installed, and comes with the Node.js world-with npm, Gulp, and Grunt. We can also install it as a Node module by using this link https://www.npmjs.com/package/bower so that we can use it without Visual Studio with another IDE, after having installed Node.js, npm, and Git.