Manually removing a dependency from bower.json should delete the corresponding folder from the directory defined in .bowerrc (wwwroot/lib by default). The Manage Bower Packages dialog does do this. As a power user, I'd expect manually editing the bower.json file to have feature parity with the Manage Bower Packages dialog.
Here are the steps to reproduce:
File --> New --> Project... --> ASP.NET Core Web Application (.NET Core)
Select the Web Application template for ASP.NET Core 1.1
Open bower.json, and add a reference to Font Awesome, and save to trigger the package installation. The bower.json file should now look as follows:
Manually removing a dependency from
bower.json
should delete the corresponding folder from thedirectory
defined in.bowerrc
(wwwroot/lib
by default). The Manage Bower Packages dialog does do this. As a power user, I'd expect manually editing thebower.json
file to have feature parity with the Manage Bower Packages dialog.Here are the steps to reproduce:
File --> New --> Project... --> ASP.NET Core Web Application (.NET Core)
Select the Web Application template for ASP.NET Core 1.1
Open
bower.json
, and add a reference to Font Awesome, and save to trigger the package installation. Thebower.json
file should now look as follows:Notice that the
wwwroot\lib\font-awesome
folder now exists in Solution Explorer.Manually remove the Font Awesome dependency from
bower.json
, and save. Yourbower.json
file now looks like this:Notice that the
wwwroot\lib\font-awesome
folder still exists: