Thanks for your contribution, @BrunoDF.
However I removed the bower config on purpose in this commit: 50372fa
With the latest version of NPM I don't see a need for bower anymore.

Hello @blueimp,
It seems like a great library and it's also one of the smallest out there which is also a perk.

But I'm not sure why you'd say that Bower is obsolete at this moment. In my setup we're using a few Grunt plugins that help which files from which Bower powered packages should be included in a project. If I want to do the same with NPM packages I need to have to do this entire process all over again.

Do you mind reconsidering your decision on this matter?

@harm-less
One of the best features of bower is that you can install packages from any git endpoint or even a GitHub shorthand, including providing a version:
http://bower.io/docs/api/#install

So, you're right that bower itself is not obsolete because it's still widely in use, but there is definitely no explicit need for a bower.json.