Why use Bower with Gulp?

Question

JavaScript

I meet such a practice when some third-party js libraries are installed through bower, I would like to understand why they do this if they can be installed as npm packages using Gulp. Thank you.

Answer 1

Different developers have this or that experience and this or that seniority. Accordingly, if it is already easier for you to use Gulp now, and the Bower developers themselves no longer recommend using it to install packages, then you are using Gulp. But someone started earlier, or just first encountered Bower, and began to use it initially.
It makes no practical sense to use it at the moment, it used to make sense when Bower was recommended to use for packages for the front, and npm (no matter how, through Gulp or directly) to use for the backend - this was due to the fact that the first pulled the dependencies for each package into his personal folder, they were installed in the public folder, and thus the folders with packages for the front were cleaner, and the dependent packages were shared.
But at the same time, it also makes no sense to use Gulp for package management everywhere, since for simple projects this is plus one tool that is not a fact that is needed. It will be easier for someone to use a pure package.json and just specify in the instructions of their project that they need to start installing packages from it.