Lot of dependencies

[danigb]

Hi @dfcreative,

I've just tried to use the new audio-loader 0.6.0 and I took more than 10 seconds to install on my computer... And I don't think that's a good user experience, so I would love to solve it.

The only solution I can find is split this module in two: one for browser and other one for node, but I'm open to suggestions.

What do you think?

[dy]

Hi @danigb. I guess you're right. It is difficult to maintain 2 versions of the same code though

[danigb]

Hi,

I'm not thinking in maintain two version on the same code. For this I'm thinking in two options:

1. Split the code in two modules. Something like audio-loader for browser, and audio-load for node that depends on the previous one and adds the node support (something like extracting the current index.jsfile). Or maybe three modules: to-audio-buffer to make the conversions, and two modules, one for browser and other for node.
2. Release two npm packages using the same codebase.

[dy]

I was planning to use audio-load for extending audio-loader to support streamed loading, like soundcloud streams. That could make audio work with streamed sources, what would be sweet. So I can just make audio-load a node/etc wrapper for audio-loader, that would solve the issue.