Troubleshooting front-end pipeline failures in AEM as a Cloud Service

Ensure package-lock.json exists in the ui.frontend module and is committed to your repository.

Regenerate package-lock.json and node_modules using a Linux environment (use Windows Subsystem for Linux or Docker). To reproduce and resolve platform-specific dependency issues for FE-only pipelines, use the following commands in a WSL terminal:  

cd /path/to/your/project
rm -rf package-lock.json node_modules
npm install
git add package-lock.json
git commit -m "Regenerate package-lock.json on Linux"

 
Or run in a Linux container:
 

docker run --rm -v $(pwd):/app -w /app node:16-alpine \
  sh -c "rm -rf node_modules package-lock.json && npm install"

Update outdated dependencies including Jest, Storybook, and Webpack.

Use npm audit with production and critical audit level flags to identify remaining dependency issues. For example: npm audit --production --audit-level=critical

Commit the regenerated package-lock.json file from the Linux environment to your repository.

Push changes to the branch used by the FE-only pipeline.

Rerun the FE-only pipeline in Cloud Manager.

Address any ESLint/code-style errors reported during the build process; all lint errors must be resolved for successful deployment.

If necessary for validation purposes only, temporarily remove linting from the build script in package.json. However, this is not recommended for production use.

Verify that the build step completes successfully without dependency or linting errors.

If the deployment succeeds but your site’s styles and scripts do not load, check Dispatcher settings and CDN configuration. Make sure your enabled vhost includes the correct ServerAlias for the static domain. For steps, refer to Frontend pipeline deployment breaks the website.

If the pipeline fails with BUILD_NPM_AUDIT_ERROR, remove any conflicting SiteConfig or HtmlPageItemsConfig nodes. For steps, refer to How to resolve BUILD_NPM_AUDIT_ERROR in AEM as a Cloud Service front-end pipeline.