I guess the native analogy is dynamically linked libraries. I imagine
doing something similar in the context of component would be somewhat
complicated.
One solution would have the "dynamically linked" libraries register
themselves on some global object, and have the require reference that
object. Then you would need some way to specify which libs are dynamic
in the component.json. Then you could have a custom builder build a
separate .js file for the dynamic shared libraries.
Kind of crazy but I imagine you could do it with a custom builder.
I have a feeling spdy + es6 modules would make this easier...
> --
> You received this message because you are subscribed to the Google Groups
> "component" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
componentjs...@googlegroups.com.
> For more options, visit
https://groups.google.com/d/optout.