how many async-modules can js-app practically load?

kai zhu kaizhu256 at gmail.com
Thu May 23 14:49:03 UTC 2019


actually, i admit i don't know what i'm talking about.  just generally
confused (through ignorance) on how large-scale es-module dependencies
resolve when loaded/imported asynchronously.

On Wed, May 22, 2019 at 10:42 PM Logan Smyth <loganfsmyth at gmail.com> wrote:

> Can you elaborate on what loading state you need to keep track of? What is
> the bottleneck that you run into? Also to be sure, when you say async-load,
> do you mean `import()`?
>
> On Wed, May 22, 2019, 20:17 kai zhu <kaizhu256 at gmail.com> wrote:
>
>> i don't use es-modules.
>> but with amd/requirejs, I start having trouble with
>> module-initializations in nodejs/browser at ~5 async modules (that may or
>> may not have circular-references).  10 would be hard, and 20 would be near
>> inhuman for me.
>>
>> can we say its somewhat impractical for most applications to load more
>> than 50 async modules (with some of them having circular-references)?  and
>> perhaps better design/spec module-loading mechanisms with this usability
>> concern in mind?
>>
>> p.s. its also impractical for me to async-load 5 or more modules without
>> using globalThis to keep track of each module's loading-state.
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20190523/7b6e2a2e/attachment.html>


More information about the es-discuss mailing list