Hello everyone!
Teammate got next problem:
npx qx compile – works if build command is performed before.
Listed below commands are getting error messages when performed.
Main question is "How to do build in these circumstances"?
1st command:D:\test\MYAP>npx qx deploy
Source maps are not being deployed, see --source-maps command line option Incremental compilation - this is faster but may preserve old artifacts, it is recommended to use --clean command line option Error:
Error: Error in property libraryPoPolicy of class qx.tool.compiler.targets.BuildTarget in method $$setLibraryPoPolicyImpl with incoming value 'undefined': Undefined value is not allowed!
2nd command:D:\test\MYAP>npx qx deploy --clean
Source maps are not being deployed, see --source-maps command line option Error:
Error: Error in property libraryPoPolicy of class qx.tool.compiler.targets.BuildTarget in method $$setLibraryPoPolicyImpl with incoming value 'undefined': Undefined value is not allowed!
In addition my teammate faces the following trace:at Object.error (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:13176:15)
at wrapper.set (eval at __installFunctionFromCode (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:13217:36), <anonymous>:3:110)
at wrapper.eval [as $$setLibraryPoPolicyImpl] (eval at __installFunctionFromCode (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:13217:36), <anonymous>:3:540)
at wrapper.eval [as setLibraryPoPolicy] (eval at __installFunctionFromCode (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:13217:36), <anonymous>:3:31)
at wrapper.eval (eval at __attachPropertyMethods (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:13065:28), <anonymous>:3:114)
at targetConfigs.forEach.targetConfig (D:\test\node_modules\@qooxdoo\compiler\source\class\qx\tool\cli\commands\Compile.js:675:16)
at Array.forEach (D:\test\node_modules\@qooxdoo\compiler\node_modules\@qooxdoo\framework\lib\qx_server\boot.js:10169:22)
at wrapper.createMakersFromConfig (D:\test\node_modules\@qooxdoo\compiler\source\class\qx\tool\cli\commands\Compile.js:633:21)
What advice can I give him?
qx deploy which might result in some temporary instability - thanks for reporting any buggy behavior.
It got fixed with this qooxdoo/qooxdoo-compiler#694 .
And we can open bug issue a little bit later with more thorough narration if the problem doesn't fix on the latest version of compiler.
If it's will be fine I will write about it here …
Got answer from teammate about wrote above issue.
Here it is:
npx qx deploy – now it works but …
Incremental compilation - this is faster but may preserve old artifacts, it is recommended to use --clean command line option ERROR: No deploy dir configured! Use --out parameter or deployPath target property in compile.json.
When using npx qx deploy and
npx qx deploy --clean
I expect to see prepared build in D:\test\compiled\build directory. But size of build folder a little bit less than D:\test\compiled\source folder.
If I execute npx qx debloy --out=D:\test\BUILD I getting build folder in this directory.
compile.json contents:"targets": [
{
"type": "source",
"outputPath": "compiled/source",
"bundle": {
"include": "qx.*"
}
},
{
"type": "build",
"outputPath": "compiled/build"
}]
As I expect I had to write deployPath somewhere there. But why is it not set automatically during creating of new app process like it set in "outputPath":"compiled/build"?
Extra information that may be useful:
D:\test\compiled\source - size of this dir is around 21MB.
D:\test\compiled\build - around 17 MB.
D:\test\BUILD - around 1 MB.
Should I open bug issue about this?
Excuse my English, I speak Spanish.
When I run "npx qx test" on my build server I see an error:
[exec] qxl.testtapper.Application: error: FATAL Syntax error: /var/lib/jenkins/jobs/build/qx_packages/qooxdoo_qxl_testtapper_v0_5_1/source/class/qxl/testtapper/Application.js: Cannot read property 'startsWith' of undefined
Hi everyone,
When I run "npx qx test" on my build server I see an error:
[exec] qxl.testtapper.Application: error: FATAL Syntax error: /var/lib/jenkins/jobs/build/qx_packages/qooxdoo_qxl_testtapper_v0_5_1/source/class/qxl/testtapper/Application.js: Cannot read property 'startsWith' of undefined
Anyone? This is kinda show stopper for us :(
build version of the code using name mangling. The new compiler only recently started also enforcing this policy. We had some internal discussion as to whether it was actually necessary, since surely nobody would try to access a private variable from outside a class ... :)
Hi everyone,
When I run "npx qx test" on my build server I see an error:
[exec] qxl.testtapper.Application: error: FATAL Syntax error: /var/lib/jenkins/jobs/build/qx_packages/qooxdoo_qxl_testtapper_v0_5_1/source/class/qxl/testtapper/Application.js: Cannot read property 'startsWith' of undefined
That happens cause in class qxl.testtapper.Application we have a code like this:let [testClass, ...testName] = test.split(":");
when compiler process it in qx/tool/compiler/ClassFile.js it falls in method encodePrivate when processing "ArrayPattern" - it assumes that prop has a property "name" (line 1747), but it should check prop.argument.name instead.
see:
{
"type": "RestElement",
"start": 6591,
"end": 6602,
"loc": {
"start": {
"line": 200,
"column": 34
},
"end": {
"line": 200,
"column": 45
}
},
"argument": {
"type": "Identifier",
"start": 6594,
"end": 6602,
"loc": {
"start": {
"line": 200,
"column": 37
},
"end": {
"line": 200,
"column": 45
},
"identifierName": "testName"
},
"name": "testName"
}
}
Hello everyone, I have a question regarding resourceloading: I need to add a suffix for every resource request. The suffix is dynamically generated and is inserted into index.html from where I can retrieve it. Looking at the source, I tried setting
qx.util.LibraryManager.getInstance().set("qx", "resourceUri", "resource/" + suffix);
qx.util.LibraryManager.getInstance().set("myapp", "resourceUri", "resource/" + suffix);first thing in Application.main which seems to do the trick.
Is this the right approach?
1 reply
