@izs whats is the current thought re: peer Deps
-
-
Replying to @stefanpenner
@stefanpenner@izs we really want to distribute Ember to use in node, but we have module state that really can't be duped.1 reply 1 retweet 2 likes -
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 @domenic
@domenic@stefanpenner@wycats@izs Presumably will be possible to enforce deterministic no-dupe behaviour? (could error on conflict)2 replies 0 retweets 0 likes
@theefer @domenic @stefanpenner @izs The blunt force instrument of a Highlander rule (there can be only one) isn't optimal, but bare minimum
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.