On Wed, Jul 9, 2014 at 1:57 PM, Jussi Kalliokoski
jussi.kallioko...@gmail.com wrote:
...
I proposed (it was less of a proposal though, more an idea or an example
to spur better ideas) that we had a single dynamic exportable per each
module, and that could be an object, function, undefined
On Thu, Jul 10, 2014 at 6:40 PM, John Barton johnjbar...@google.com wrote:
On Wed, Jul 9, 2014 at 1:57 PM, Jussi Kalliokoski
jussi.kallioko...@gmail.com wrote:
...
I proposed (it was less of a proposal though, more an idea or an example
to spur better ideas) that we had a single dynamic
John is right, all the use cases you've mentioned can be solved with the
current design. Here is an example of a loader extension that implements
conditional loading:
https://gist.github.com/caridy/1a67aaf433ae03a42a8b
This particular implementation relies on the `trigger` configuration
On the ModuleImport thread, I pretty much derailed [1] the conversation
with poor argumentation which lead to the discussion drying out. But the
more I think about it, the more important I feel my concern was so I
figured I'd have another shot at it.
The problem I was describing is that, as with
4 matches
Mail list logo
