require Omnitone without relative paths

[brianchirls]

The only referenced external dependency is Omnitone, which is imported via a relative path pointing to the library under node_modules as:

const Omnitone = require('../node_modules/omnitone/build/omnitone.js');

Since Omnitone is compiled into this library's build file (which is probably fine), anyone using resonance who also might want to use Omnitone would be forced to load two copies of it. One might try to reference the resonance source files, which are included in the npm package, but since Omnitone is included as above, that won't solve the problem.

Please change this to:

const Omnitone = require('omnitone');

Since you're building with webpack, this should allow builds that use the source files to use their own copy of Omnitone, without changing the build output from this repo. It should also allow dependents to use the latest version of Omnitone without having to wait for an upgrade in this repo.

Thanks

[hoch]

I think this might be the case where RA used a modified version of Omnitone, so importing it from the local package was necessary. (while @drewbitllama and I were hacking the code to make HOA work) I think we're past the development phase, so it makes sense to update the dependency as you suggested.