ok thanks,
Let's see what happens.
In the meanwhile, any idea from folks regarding this issue is welcome

El mié., 26 ago. 2020 a las 13:56, Christofer Dutz (<
[email protected]>) escribió:

> Hi Carlos,
>
> I asked a question in their forum:
> https://groups.google.com/g/closure-library-discuss/c/yBHT1UmRM4M
>
> Let's hope this is not completely dead (Discussions there don't seem to
> happen too regularly)
>
> Chris
>
>
> Am 26.08.20, 13:51 schrieb "Carlos Rovira" <[email protected]>:
>
>     Hi Chris,
>
>     Did you check how closure folks deal with this situation? I guess we
>     shouldn't be the first to face this problem. Having that code out of
> our
>     codebase seems complicated to deal with. And I prefer to avoid the
> queue
>     loading idea if possible.
>
>     Thanks
>
>
>
>     El mié., 26 ago. 2020 a las 12:33, Christofer Dutz (<
>     [email protected]>) escribió:
>
>     > Hi all,
>     >
>     > just opening a new thread as the content of my relative path thread
>     > changed quite a bit over time.
>     >
>     > Yesterday I figured out that if you try loading multiple modules at
> the
>     > same time (by setting autoLoad=true or by triggering more than one
> to load
>     > at once) you will have issues.
>     >
>     > The reason is that for the first module, closure will make a list of
>     > missing resources and start loading them … then comes the second
> module and
>     > again it loads the list of missing resources.
>     > Unfortunately it might load resources, the first module already
> requested,
>     > but which have not been received or processed yet. So when a
> duplicate
>     > resource is returned to the client, and the client processes this,
> the user
>     > gets an ugly “this resource has already been registered” error.
>     >
>     > Unfortunately this is in the closure code … so not quite sure which
>     > strategy we should follow.
>     >
>     > I know that using js-debug is not ideal, but during development time
> I
>     > need to do it in order to be able to debug things.
>     >
>     > Still have to dig into how to get the js-release working.
>     >
>     > Chris
>     >
>     >
>
>     --
>     Carlos Rovira
>     http://about.me/carlosrovira
>
>

-- 
Carlos Rovira
http://about.me/carlosrovira

Reply via email to