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 :)
@phillipskevin et al. In an attempt to learn about bundlers other than steal with canjs, I put together a small demo @ https://github.com/DaveO-Home/embedded-acceptance-tests. I think it works....
So I see that react is more performant in this example now? https://output.jsbin.com/wotevub/2 Are you guys seeing the same?
This is on Chrome
It's consistent with benchmarks provided by others since the release of React 16
Ah Okay. Are there any comparisons with Canjs/React 16/Angular 4?
I haven't seen any. I don't know if it's my own browsing patterns or that performance benchmarks just aren't so compelling anymore, but they don't come across my radar much.
