greenkeeper[bot] on core-js-3.5.0
chore(package): update core-js … (compare)
greenkeeper[bot] on can-observable-mixin-1.0.7
fix(package): update can-observ… (compare)
cherifGsoul on update-infrastructure-page
cherifGsoul on master
Update infrastructure page with… (compare)
cherifGsoul on update-infrastructure-page
Fix typos (compare)
cherifGsoul on document-inserted-removed-can6
Add inserted/removed events to … (compare)
greenkeeper[bot] on can-view-live-5.0.1
fix(package): update can-view-l… (compare)
I was thinking about this issue, that I've asked before and got the idea... what if I list can
as peerDependency
for my components ? I mean I know that my component should work with ...can 3.x
and the only thing that might brake my component is some API
change which is fairly rare case. But if I do this way I'll avoid this "2 versions of something found" because entity-details-component
will use "host" packages. Well at least I expect it to do this :)