Ambiente
Experience Manager as a Cloud Service
Problema/Sintomas
A execução do pipeline está falhando durante a etapa de build, devido a erros no ui.frontend
código.
Você observa mensagens de ERRO como as abaixo na build.log
arquivo:
12:52:44,558 Exec Stream Pumper INFO ERROR in /build_root/build/program/ui.frontend/node_modules/@types/node/ts4.8/util.d.ts
12:52:44,559 Exec Stream Pumper INFO tsl ERROR in /build_root/build/program/ui.frontend/node_modules/@types/node/ts4.8/util.d.ts(1485,42)
12:52:44,561 Exec Stream Pumper INFO TS1005: ',' expected.
12:52:44,561 Exec Stream Pumper INFO
12:52:44,561 Exec Stream Pumper INFO ERROR in /build_root/build/program/ui.frontend/node_modules/@types/node/ts4.8/util.d.ts
12:52:44,562 Exec Stream Pumper INFO tsl ERROR in /build_root/build/program/ui.frontend/node_modules/@types/node/ts4.8/util.d.ts(1485,44)
12:52:44,563 Exec Stream Pumper INFO TS1068: Unexpected token. A constructor, method, accessor, or property was expected.
12:52:44,563 Exec Stream Pumper INFO
12:52:44,563 Exec Stream Pumper INFO ERROR in /build_root/build/program/ui.frontend/node_modules/@types/node/ts4.8/util.d.ts
12:52:44,564 Exec Stream Pumper INFO tsl ERROR in /build_root/build/program/ui.frontend/node_modules/@types/node/ts4.8/util.d.ts(1485,57)
12:52:44,564 Exec Stream Pumper INFO TS1005: ';' expected.
12:52:44,564 Exec Stream Pumper INFO
Siga as etapas abaixo:
Localize na raiz do Git Repo, o arquivo pom.xml,
e encontrar a versão do nó, por exemplo, nodeVersionv10.13.0/nodeVersion
Localizar ui.frontend/package.json,
e adicionar o já presente devDependencies
objeto: por exemplo, "devDependencies":
Observação:
O “v” do nodeVersion v10.13.0 não deve ser copiado.
A versão do nó pode ser diferente no seu caso. Por exemplo: 12.22.7