Ui.frontend/POM.xml
<!-- ====================================================================== -->
<!-- P A R E N T P R O J E C T D E S C R I P T I O N -->
<!-- ====================================================================== -->
<parent>
<groupId>com.aembootcamp</groupId>
<artifactId>aem-bootcamp</artifactId>
<version>1.0.0-SNAPSHOT</version>
<relativePath>../pom.xml</relativePath>
</parent>
<!-- ====================================================================== -->
<!-- P R O J E C T D E S C R I P T I O N -->
<!-- ====================================================================== -->
<artifactId>aem-bootcamp.ui.frontend</artifactId>
<packaging>pom</packaging>
<name>AEM Bootcamp Site - UI Frontend</name>
<!-- ====================================================================== -->
<!-- B U I L D D E F I N I T I O N -->
<!-- ====================================================================== -->
<build>
<sourceDirectory>src/main/content/jcr_root</sourceDirectory>
<plugins>
<plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
<executions>
<execution>
<id>npm run prod</id>
<phase>generate-resources</phase>
<goals>
<goal>npm</goal>
</goals>
<configuration>
<arguments>run prod</arguments>
</configuration>
</execution>
</executions>
</plugin>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>single</goal>
</goals>
<configuration>
<descriptors>
<descriptor>assembly.xml</descriptor>
</descriptors>
<appendAssemblyId>false</appendAssemblyId>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
<profiles>
<profile>
<id>fedDev</id>
<activation>
<activeByDefault>false</activeByDefault>
</activation>
<build>
<plugins>
<plugin>
<groupId>com.github.eirslett</groupId>
<artifactId>frontend-maven-plugin</artifactId>
<executions>
<execution>
<id>npm run dev</id>
<phase>generate-resources</phase>
<goals>
<goal>npm</goal>
</goals>
<configuration>
<arguments>run dev</arguments>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
</project>
Solved! Go to Solution.
Views
Replies
Total Likes
Hello @Anilkumar9
The error you mentioned, "npm run prod failed," typically occurs when the npm command fails during the execution of the frontend-maven-plugin. This can happen for various reasons, such as missing dependencies, issues in your project's configuration, or problems with the npm environment. Here are some steps to troubleshoot and resolve the issue:
Check Dependencies:
Ensure that Node.js and npm are installed on your system and are accessible from the command line.Verify that you have the required dependencies listed in your project's package.json file. Make sure that all dependencies are correctly specified, and there are no syntax errors in the package.json.
Update Dependencies:
Run npm update to update your project's dependencies to their latest versions.
Clean npm Cache:
Sometimes, npm cache issues can lead to problems. You can try cleaning the npm cache by running npm cache clean -f and then running your build again.
Check Network Connection:
Ensure that your network connection is stable and that there are no firewall or proxy issues that might be blocking npm from fetching dependencies
If you can share the error log, probably will be able to help better..
Hello @Anilkumar9
The error you mentioned, "npm run prod failed," typically occurs when the npm command fails during the execution of the frontend-maven-plugin. This can happen for various reasons, such as missing dependencies, issues in your project's configuration, or problems with the npm environment. Here are some steps to troubleshoot and resolve the issue:
Check Dependencies:
Ensure that Node.js and npm are installed on your system and are accessible from the command line.Verify that you have the required dependencies listed in your project's package.json file. Make sure that all dependencies are correctly specified, and there are no syntax errors in the package.json.
Update Dependencies:
Run npm update to update your project's dependencies to their latest versions.
Clean npm Cache:
Sometimes, npm cache issues can lead to problems. You can try cleaning the npm cache by running npm cache clean -f and then running your build again.
Check Network Connection:
Ensure that your network connection is stable and that there are no firewall or proxy issues that might be blocking npm from fetching dependencies
If you can share the error log, probably will be able to help better..
Hi @Anilkumar9
Can you share the error snippet. It will help in understanding little more into the issue. Meanwhile couple of things you can try is adjusting your npm version also clearing the cache and rerun install and run .
Also check the below url
Views
Likes
Replies
Views
Likes
Replies