Support for Bower packaging

[spotshare-nick]

Wiredep as well as other tools read the bower.json file for linking purposes. Created and tested valid bower.json file.

[Krinkle]

@nblasgen Thanks for your proposal, but I'll have to decline at this time.

I do not support use of Bower. And the Bower maintainers themselves also don't recommend its use anymore. Going forward, you should use the npm registry (possibly through Yarn or Webpack).

• https://bower.io/, https://bower.io/blog/, https://github.com/bower/bower, Discussion: NPM Migration Path bower/bower#2467:

While Bower is maintained, we recommend yarn and webpack for new front-end projects!

In a related note, given the purpose of this particular project (jquery-json), I would recommend thinking twice before using it. It's purpose is to provide JSON parsing capabilities to older browsers. Virtually every modern browser (Over 98%, depending on the demographics of your target audience) implements JSON.parse and JSON.stringify as part of the JavaScript run-time.

See: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/JSON

If you need support for older browsers, I'd recommend using json2.js, from https://github.com/douglascrockford/JSON-js.

[spotshare-nick]

I fully agree, but the developers of Freeswitch have chosen to pick your library for their JSON handling. So while I could patch their code to use the JSON object (as any code that relies on new browser features should do), I found the process that much easier to just adjust your code to make the existing jquery-json bower package useable.