Expand my Community achievements bar.

Enhance your AEM Assets & Boost Your Development: [AEM Gems | June 19, 2024] Improving the Developer Experience with New APIs and Events

AEM As a cloud Service - Front End Pipeline build error - Need log path


Level 2

I have run the front end pipeline in AEM Cloud. I am getting the below error.

Error Details:

Skipping 'fsevents' build as platform linux is not supported
npm WARN lifecycle aem-maven-archetype@1.0.0~prepare: cannot run in wd aem-maven-archetype@1.0.0 cd ../ && husky install ./ui.frontend/.husky (wd=/build_root/build/etisalat-p42155/ui.frontend)
added 2482 packages in 53.19s

[BUILD] Running npm build command(s)
Executing command npm --progress false run build
npm ERR! missing script: build

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2023-02-14T15_09_40_626Z-debug.log.


Where can I see the full error log (/root/.npm/_logs/2023-02-14T15_09_40_626Z-debug.log). Could any one  please help me to find the log file path.


4 Replies


Employee Advisor

Hi @kamsdurai ,


Looks like one of your npm dependencies is causing this failure.


You can't access the path "root/.npm/" as it's on the docker image. I've seen such errors when platform-specific plugins were added as dependencies.


I would recommend that you download the build logs from the cloud manager and check the full trace. (Maybe you can add more lines of error in your question to get better answers).


I would also recommend looking at the latest archetype



Alternatively, you can also open a support ticket if you have already checked the above points.


Hope that helps!






Community Advisor

I think you should check the package.json for 

npm ERR! missing script: build 

npm --progress false run build


You can access the logs using postman or aio cli,  e.g.



npm logs you can't access in cloud manager.

Arun Patidar


Level 2

Thanks for your response 

Full stack build is working fine in AEM cloud. But while running the Front end build,  then only it is throwing the above error. 


Level 1

This is because you need to configure your front-end pipeline directory into your frontend maven module. I guess you're repository root don't have the package.json with npm script called build, it should be inside a maven submodule. Change pipeline location to your front-end maven module and it will work.