Hi,
I am working on spa react project, my local aem instance version is 6.5.12.0
I created project using this cmnd
mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate
-D archetypeGroupId=com.adobe.aem
-D archetypeArtifactId=aem-project-archetype
-D archetypeVersion=35
-D appTitle="Helloreact"
-D appId="helloreact"
-D artifactId="helloreact"
-D groupId="com.adobe.aem.helloreact"
-D frontendModule="react"
-D aemVersion="6.5.5"
I created custom component then after I created customcomonent.js, i did mapping the components then after I run the cmnd mvn clean install -PautoInstallPackage then I am getting the below error
Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.12.0:npm (npm run build) on project helloreact.ui.frontend: Failed to run task: 'npm run build' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1
these are also I found
npm ERR! code ELIFECYCLE
[INFO] npm ERR! errno 1
[INFO] npm ERR! helloreact@0.1.0 build: `react-scripts build && clientlib --verbose`
[INFO] npm ERR! Exit status 1
[INFO] npm ERR!
[INFO] npm ERR! Failed at the helloreact@0.1.0 build script.
[INFO] npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
[INFO]
[INFO] npm ERR! A complete log of this run can be found in:
Can anyone help me
Views
Replies
Total Likes
Hi @SantoshSai ,
I am having the same configuration as mentioned in the shared article like this
<plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
<version>1.7.6</version>
<configuration>
<nodeVersion>v10.13.0</nodeVersion>
<npmVersion>6.9.0</npmVersion>
</configuration>
<executions>
<execution>
<id>install node and npm</id>
<goals>
<goal>install-node-and-npm</goal>
</goals>
</execution>
<execution>
<id>npm install</id>
<goals>
<goal>npm</goal>
</goals>
</execution>
</executions>
</plugin>
in my local system im having node v1417.5 and npm is 6.14.4 I also tried updating node and npm versions in pom.xml as like in my local machine but this also didnt solve my issue.