Closed rwjblue closed 10 years ago
SOOOOO bad, but they feel SOOOOO good. :stuck_out_tongue:
Also, totally up to you on this one, if you don't want to pull in ember-cli-pretender (understandable), then I'll do another PR to fixup/cleanup the way it is done in repo.
Just feels bad to have to do this for each repo (but wrapper packages feel bad too, I know).
@rwjblue I've been thinking about this, if the addon wrapper actually just had pretender & other deps in its bower.json file then why can't we run bower install
for the addon after node installs? This would cleanly add those deps to bower_components
and the wrapper's role could simply be to merge with ember-cli apps
The addon should pull whats in its own bower_components into the vendor tree
Yes, I worked a bit on this for ember-cli-qunit.
The only caveat is that it uses it's own packages bower_components directory (so it is not in the make consuming application dir or bower.json).
I can tweak ember-cli-pretender to do this in the morning.
Yeah, I think we are on the same page. I like the way we ended up on ember-cli-qunit (except that we have to depend on bower in the addon, but that isn't a HUGE deal).
Updated ember-cli-pretender to remove all vendored code. Now it simply calls bower install
in a postinstall
hook as discussed.
This PR has been updated to reflect the correct version.
@bcardarella - ping
yeah I saw it, I want to wrap up the relationships stuff before I pull in. Maybe tonight (if I'm lucky)
@rwjblue requires rebase
I thought these wrappers were bad?