Error related to ecmascript 6 while building pipeline in cloud manager for AEM as cloud service

Forum|Forum|5 years ago
June 10, 2020
3 replies
4536 views

I am building and deploying a project on AEM cloud instance via cloud manager deploy pipeline for the first time.

and the build images step is failing with lots of errors like the one below related to libs components.

Jun 10, 2020 8:58:03 AM com.google.javascript.jscomp.LoggerErrorManager println
SEVERE: /libs/cq/ups/rte/plugin.js:574: ERROR - This language feature is only supported for ECMASCRIPT6 mode or better: const declaration.
const context = this.editorKernel.editContext;

Any body faced same issue or any pointers?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

Best answer by nidhip010816

Hello @asn_india

The /libs/clientlibs/granite/coralui2 node has a jsProcessor property set to "min:gcc". This means that this property takes precedence over the configuration in the HTML Library Manager. And this somewhat explains this - "This language feature is only supported for ECMASCRIPT6 mode"

Although, It would be great if you log a ticket where a Support Engineer could work with you by looking into your Cloud environment.

Hope this helps!

Warm regards,

Nidz

nidhip010816Accepted solution

Employee

Hello @asn_india

The /libs/clientlibs/granite/coralui2 node has a jsProcessor property set to "min:gcc". This means that this property takes precedence over the configuration in the HTML Library Manager. And this somewhat explains this - "This language feature is only supported for ECMASCRIPT6 mode"

Although, It would be great if you log a ticket where a Support Engineer could work with you by looking into your Cloud environment.

Hope this helps!

Warm regards,

Nidz

asn_indiaAuthor

New Participant

Thank You Nidhi....That seems to be the issue.

I tried specifying options to make default as ECMASCRIPT6 at our project's clientlibs(/apps ones) and errors related to those clientlibs were gone in next deploy attempt.

For libs though I wont be able to do so....so trying to put up a osgiconfig for HTML Library Manager...lets see if that solves the problem with libs one's.