Ambiente
Experience Manager as a Cloud Service
Problema/Sintomi
L’esecuzione della pipeline non riesce durante il passaggio della build, a causa di errori nel ui.frontend
codice.
Si osservano messaggi ERROR come il seguente nel build.log
file:
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
Segui i passaggi descritti qui sotto:
Individua nella directory principale del repository Git, il file pom.xml,
e trovare la versione del nodo, ad esempio, nodeVersionv10.13.0/nodeVersion
Individua ui.frontend/package.json,
e aggiungi il già presente devDependencies
oggetto: ad esempio, "devDependencies":
Nota:
La “v” in nodeVersion v10.13.0 non deve essere copiata.
La versione del nodo, nel tuo specifico caso, potrebbe essere diversa. Ad esempio: 12.22.7