@stefanpenner @izs we really want to distribute Ember to use in node, but we have module state that really can't be duped.
-
-
Replying to @wycats
@wycats@stefanpenner@izs my opinion is there should be a separate flag saying "allowDupes": false, peer deps are not meant for this.2 replies 0 retweets 0 likes -
Replying to @domenic
@domenic@stefanpenner@izs What other options do we have today?1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats@stefanpenner@izs post-install tool to check for dupes and error.1 reply 0 retweets 0 likes -
Replying to @domenic
@domenic@stefanpenner@izs I am crying. Also I don't want an error; I just want a single module shared!2 replies 0 retweets 0 likes -
Replying to @wycats
@wycats@stefanpenner@izs don't share if packages require incompatible versions, that is bad.2 replies 0 retweets 0 likes -
Replying to @stefanpenner
@stefanpenner@wycats@izs false? npm dedupe/npm v3 will remove dupes on no conflict. I assumed you wanted a way to catch conflicts.2 replies 0 retweets 0 likes -
Replying to @domenic1 reply 0 retweets 0 likes
-
Replying to @stefanpenner
@stefanpenner@wycats@izs yep, not yet, in the meantime use npm dedupe to emulate.2 replies 0 retweets 0 likes
@domenic @stefanpenner @izs we just want to be able to ship a cluster of compatible module with multiple deps on say, ember-metal, and share
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.