Unmet peer dependency

[dustinfarris]

I want to hijack some of the code here for a non-webpack Ember/Cashay integration I'm working on. package.json specifies webpack as a peer dependency which I would rather not be required for what I'm doing.

[dustinfarris]

@mattkrick what are your thoughts on using this as repo as a toolbelt for non-webpack integrations? Is that changing the scope here inappropriately? Would it be better form for me to create a similar Ember-specific "loader" repo (essentially copy+pasting everything here, but with Ember scaffolding)?

[mattkrick]

Oh yeah, i would definitely avoid any work on this repo, it's just a bunch of dead code. I originally planned to break out the webpack loader as a separate npm package, but realized it was so much cleaner just doing it inside cashay, plus if you use tree-shaking accordingly, it won't increase the client payload. The code inside cashay/schema is more up to date.

[dustinfarris]

Great, thanks.