In their own words:<\/p>\n
Though it doesn\u2019t say it explicitly, it implies that Bower is deprecated. Existing projects that depend on package management via Bower will continue to work for the time being; but it\u2019s recommended that new projects should not take a dependency on Bower.<\/p>\n While there are other useful package managers, as Bower points out (e.g. npm), most are designed to handle a variety of tasks, which adds unnecessary complexity when you only need them for a single task (acquiring client-side libraries). So, here at Visual Studio, we decided to create a new tool that would be as simple as possible for specifically addressing the need to acquire client-side content for web applications. Hence, the introduction of \u201cLibrary Manager\u201d.<\/p>\n Library Manager (“LibMan” for short) is Visual Studio\u2019s new client-side static content management system. Designed as a replacement for Bower and npm, LibMan helps users find and fetch library files from an external source (like CDNJS<\/a>) or from any file system library catalog.<\/p>\n You can specify the library files required for your project by adding entries to the LibMan configuration file – libman.json. See the image below; it shows an example libman.json file in which some jQuery files are added to the wwwroot\/lib directory.<\/p>\n![\"Message](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2018\/04\/bower-recommends-yarn-2.png\")
<\/a><\/p>\nIntroducing Library Manager<\/h3>\n
![\"Example](\"https:\/\/devblogs.microsoft.com\/aspnet\/wp-content\/uploads\/sites\/16\/2018\/04\/example-libman.json_-1.png\")
<\/a><\/p>\n