ReferenceError: $jscomp is not defined

Get help with testing, discuss unit testing strategies etc.
Post Reply
User avatar
solo
Posts: 2
Joined: Wed Jan 30, 2019 4:04 pm

ReferenceError: $jscomp is not defined

Post by solo » Thu Jan 31, 2019 1:21 pm

Hi,

Just downloaded yesterday the latest trial version of Siesta, v5.1.1, but can't run any launcher.
My server hosts siesta folder, my console is at _SIESTA_/bin folder. I run:

> ./webdriver.bat http://localhost:8888/examples/sencha-e ... no-ui.html

After several seconds it stops. No console output, just this:

> cat ./webdriver.log

C:\...\Siesta\bin\siesta-launcher-all.js:220
"");process.env.NODE_TLS_REJECT_UNAUTHORIZED="0";var p=require("nyc/lib/source-maps"),r=p.prototype.extractAndRegister;p.prototype.extractAndRegister=function(){try{return r.apply(this,arguments)}catch(a){return null}};p=function(a){g.Readable.apply(this,arguments)};$jscomp.inherits(p,g.Readable);p.prototype._read=function(){};Role("Siesta.Launcher.Role.CanLaunchInstrumentationProxy",{does:["Siesta.Launcher.Role.CanWorkWithNyc"],requires:["debug"],has:{instrumentationProxyPort:0,instrumentationHttpsServerPort:0,

^

ReferenceError: $jscomp is not defined
at C:\Development\git\ufo\Frontend\Siesta\bin\siesta-launcher-all.js:220:268
at Object.<anonymous> (C:\Development\git\ufo\Frontend\Siesta\bin\siesta-launcher-all.js:234:399)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Module.require (module.js:596:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (C:\Development\git\ufo\Frontend\Siesta\bin\webdriver-launcher.js:19:1)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)

Please help.

Regards,
Alexei

User avatar
nickolay
Core Developer
Core Developer
Posts: 3329
Joined: Mon May 16, 2011 10:48 am

Re: ReferenceError: $jscomp is not defined

Post by nickolay » Thu Jan 31, 2019 1:25 pm

Thanks for the report, we'll investigate shortly.
We offer training in both Ext JS and our products, read more here.
Read the API documentation

User avatar
nickolay
Core Developer
Core Developer
Posts: 3329
Joined: Mon May 16, 2011 10:48 am

Re: ReferenceError: $jscomp is not defined

Post by nickolay » Thu Jan 31, 2019 1:46 pm

Confirmed. It seems the Google Closure, has "optimized" the code

Code: Select all

class GeneralReadable extends stream.Readable {
    _read () {}
}
to

Code: Select all

p=function(a){g.Readable.apply(this,arguments)};$jscomp.inherits(p,g.Readable);p.prototype._read=function(){}
And did not add the $jscomp to the output.

We'll fix shortly, stay tuned.
We offer training in both Ext JS and our products, read more here.
Read the API documentation

User avatar
nickolay
Core Developer
Core Developer
Posts: 3329
Joined: Mon May 16, 2011 10:48 am

Re: ReferenceError: $jscomp is not defined

Post by nickolay » Thu Jan 31, 2019 2:32 pm

Uploaded a new trial package with the fix, please re-download and let me know how it works.
We offer training in both Ext JS and our products, read more here.
Read the API documentation

User avatar
solo
Posts: 2
Joined: Wed Jan 30, 2019 4:04 pm

Re: ReferenceError: $jscomp is not defined

Post by solo » Thu Jan 31, 2019 2:33 pm

You're fast! Thanks!

Post Reply