LABjs - error loading scripts

0

Please do not show me the link documentation link or examples taken from there because this I have already read, and I honestly do not understand "that is, the page loads about three times and then one of the error.

So I'm believing that the problem is asynchronous, I've already gotten a lot in the order of the scripts, putting .wait at all, only in a few, and finally nothing at all follows the last test:

$LAB            
.script('../js/date.js')                                        // NAO TEM DEPENDENCIA
.script('../js/plugin/jquery.insc.estadual.js')                 // NAO TEM DEPENDENCIA            
.script('../js/node/socket.io.js').wait()                       // NAO TEM DEPENDENCIA
.script('../js/js_1.9/jquery-1.8.2.js').wait()                  // NAO TEM DEPENDENCIA
.script('../js/jquery.shortcuts.min.js')                        // DEPENDE DE JQUERY
.script('../js/jquery.meiomask.js')                             // DEPENDE DE JQUERY
.script('../lib/jquery.validate.js')                            // DEPENDE DE JQUERY
.script('../js/js_1.9/jquery-ui-1.9.1.custom.min.js').wait()    // DEPENDE DE JQUERY                        
.script('../js/dataBr.js')                                      // DEPENDE DE JQUERY E JQUERY-UI
.script('../js/plugin/jquery.zoomooz.js')                       // DEPENDE DE JQUERY E JQUERY-UI                        
.script('../js/custom_jquery.js?nocache='+Math.random())        // DEPENDE DE JQUERY E JQUERY-UI                            
.script('../js/principal.js?nocache='+Math.random());           // DEPENDE DE JQUERY , JQUERY-UI E SOCKET.IO

The errors that appear sporadically are:

sometimesonlythese:

Sometimesonlyone:

More lost than early in the shootout, can anyone give me a hand?

    
asked by anonymous 19.08.2015 / 16:07

1 answer

0

Well, I'm going to put the solution here, so that others do not have to waste time when this happens, well strange things happen in this life, and that was one of the strange cases, maybe someone knows why these things,

First of all, this test was done with firebug on firefox , I really like it and I always use it and I'll probably always use it, the code likewise got me in the head of testing with chrome with the default developer tools, to my surprise all the repeated times I tested were successful.

firefox I took the default developer tool and tested it again and it worked fine too, but before posting my answer and putting all the blame on firebug I did other tests, and to my surprise the problem could be presented in both browsers with any tool that was turned on for all monitoring options.

In other words, when enabled console, script, network and cookie with all available options, this error was generated, even with these monitors connected, the time to open the page was much higher without those monitors is around 400ms, with the monitors connected it would take 3 seconds to load and many times these errors occurred, now why this maybe even pertinent in another question

    
20.08.2015 / 19:05