title: Is it still appropriate to use Bower to install Bootstrap instead of via NPM or NuGet?
body: <p>I'm checking out tons of blogs like <a href="https://docs.microsoft.com/en-us/aspnet/core/client-side/bootstrap" rel="nofollow noreferrer">this one</a> where it's explicitly stated that Bower is the preferred and recommended way install Bootstrap to my Core web app.</p>
  
  <blockquote>
    <p>The recommended way to install client-side dependencies like Bootstrap in ASP.NET Core is via Bower (using bower.json, as shown above). The use of npm/NuGet are shown to demonstrate how easily Bootstrap can be added to other kinds of web applications, including earlier versions of ASP.NET.</p>
  </blockquote>
  
  <p>Checking the date of the post seems to be settling as it's only a few weeks old but when I check e.g. the icon for dependencies and some other things, I'm getting the impression that the content might be actually a bit more aged than so.</p>
  
  <p>I've been googlearching lately and I learned that there's a shift towards fewer-simpler-smaller approach. Especially I've discovered that NPM is often recommended for managing all the packages, including Bootstrap. (Now, just because someone says so, it doesn't automatically makes it true - we need to ask <strong>why</strong> would the one or the other approach be more advantageous.)</p>
  
  <p>Question - what's the downside of using Bower to manage Bootstrap instead of installing it with NPM and omitting Bower all together?</p>