Provide access to bundled libraries when run in browser

[lidel]

I wonder if there are any cons to exposing libraries such as is-ipfs, multiaddr and multihashes under ipfs.util.lib.* or maybe only in browser-specific build under windows.ipfsLibs ?

I feel people who use browserified artifact would really appreciate it as it would remove code duplication in smaller projects (no need to ship library twice just to have it available as window.foo).

Perhaps there are better ways to do this that I am not aware of? Any thoughts on this?

[daviddias]

Related with ipfs/js-ipfs#525 (comment)

@lidel wanna help us achieve both?

[lidel]

I am sorry, I have limited free time and need to prioritize my activities.
This is not a blocker for me, just an inconvenience, so it does not have high priority :-)
WebExtension migration is my main focus right now.