hi all,
we are getting the below build error in a project for ui.frontend module -
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.15.0:npm (npm install) on project wknd-foundation.ui.frontend: Failed to run task: 'npm install' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 128 (Exit value: 128) -> [Help 1]
INFO] npm ERR! code 128
[INFO] npm ERR! An unknown git error occurred
[INFO] npm ERR! command git --no-replace-objects ls-remote https://tkumar11-wknd-com:***@git.cloudmanager.adobe.com/wknd/aem-cs-centralized-package-dev-file
[INFO] npm ERR! fatal: unable to access 'https://git.cloudmanager.adobe.com/wknd/aem-cs-centralized-package-dev-file/': SSL certificate problem: unable to get local issuer certificate
[ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.15.0:npm (npm install) on project wknd-foundation.ui.frontend: Failed to run task: 'npm install' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 128 (Exit value: 128) -> [Help 1]
Node version - 18.20.3
Npm version - 10.7.0
Running npm install on frontend module gives below error -
C:\wknd\aem-foundation\ui.frontend>npm install
npm error code ETARGET
npm error notarget No matching version found for @Nucleus/vue@5.18.1.
npm error notarget In most cases you or one of your dependencies are requesting
npm error notarget a package version that doesn't exist.
Solved! Go to Solution.
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
For Issue 1, you might want to disable the ssl - you can try building only the ui.frontend module after configuring via "git config --global http.sslVerify false"
This will disable SSL certificate checking for the repo.
The error message indicates an SSL certificate problem while accessing a Git repository. Specifically, the error is related to the npm install command, which is trying to fetch dependencies from a Git repository, but it cannot verify the SSL certificate.
For many companies, some firewalls need an installed SSL certificates to install the dependencies in the run time.
Here are some steps to troubleshoot and resolve this issue:
Make sure the SSL certificates are properly configured on the machine running the build. This includes updating the CA certificates.
If you're in a controlled environment and sure about the repository's authenticity, you can temporarily disable SSL verification for Git. However, this is not recommended for production environments due to security risks. Most probably you won't even have permission to do it.
Ensure you are using the latest version of the frontend-maven-plugin. There might be bug fixes or improvements that could resolve your issue.
In your pom.xml:
Ensure that the repository URL and the credentials provided are correct. Verify that the username and token (or password) are correct and have the required permissions to access the repository.
If you need to add custom CA certificates to Node.js, you can configure it by setting the NODE_EXTRA_CA_CERTS environment variable.
Check your network settings to ensure there are no proxies or firewalls blocking the connection to the Git repository. Configure your .npmrc file if you are behind a corporate proxy.
In your .npmrc file:
Download the certificates through "visit site information" and install them on your PC manually.
After applying every step, retry running your Maven build.
By following these steps, you should be able to resolve the SSL certificate issue and successfully execute the npm install command during your build process.
It looks like you're experiencing two separate issues.
Issue 1: SSL certificate problem
The first error message indicates a problem with the SSL certificate when trying to access a Git repository. This is likely due to a missing or invalid certificate in your system's truststore.
To resolve this, you can try the following:
Issue 2: npm install error (ETARGET)
The second error message indicates that npm can't find a matching version for the @Nucleus/vue package.
To resolve this, you can try the following:
Additionally, you can try updating the frontend-maven-plugin to a newer version, as the current version (1.15.0) might be outdated.
If none of these solutions work, please provide more details about your project setup, and I'll be happy to help you troubleshoot further!
For Issue 1, you might want to disable the ssl - you can try building only the ui.frontend module after configuring via "git config --global http.sslVerify false"
This will disable SSL certificate checking for the repo.
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies