Expand my Community achievements bar.

Adobe Summit 2025: AEM Session Recordings Are Live! Missed a session or want to revisit your favorites? Watch the latest recordings now.

Mark Solution

This conversation has been locked due to inactivity. Please create a new post.

SOLVED

npm install failed error

Avatar

Level 5

Hi, 

I am trying to run a maven project. But it throws the below error. I have tried many ways like changed the node verstion, installed new/updated node then ran npm install under ui.frontend but nothing works out. Can anyone tell me the solution for this ?

Tessa_learner1_0-1654765481178.png

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor and Adobe Champion

Hello @Tessa_learner1

 

It looks like you are using the latest Node and npm version which may not support some node modules that is installed from the package.json. Try to play around with the npm version and see if that works. From testing myself, I realize that the latest Node and NPM version do not work.

 

View solution in original post

6 Replies

Avatar

Community Advisor

Can you try deleting and regenrating paclage-lock.json

Arun Patidar

AEM LinksLinkedIn

Avatar

Level 5

@arunpatidar  Thanks for the suggestion. As I was using latest node version, just changed the npm version to 3.10.8 and it got worked. Thanks for your time. 

Avatar

Community Advisor

Hi @Tessa_learner1 ,

Please check below thread: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/npm-error-while-doing-clea...

Hope that helps you!

Regards,

Santosh


Santosh Sai

AEM BlogsLinkedIn


Avatar

Level 5

Thank you @SantoshSai  I have changed the npm version to 3.10.8 as mentioned in the link and it got success. Thanks for your time.

Avatar

Correct answer by
Community Advisor and Adobe Champion

Hello @Tessa_learner1

 

It looks like you are using the latest Node and npm version which may not support some node modules that is installed from the package.json. Try to play around with the npm version and see if that works. From testing myself, I realize that the latest Node and NPM version do not work.

 

Avatar

Level 5

Thank you. @BrianKasingli  Yes, I was using the latest node & npm version and I have changed only the npm version in main pom.xml and it got resolved.