aem-project-archetype
aem-project-archetype copied to clipboard
Usage of 'npm ci' for Build Pipelines
Expected Behaviour
Local build always also corresponds to CI/CD build using 'npm ci'
See for more information:
- https://docs.npmjs.com/cli/v7/commands/npm-ci/
- https://stackoverflow.com/questions/52499617/what-is-the-difference-between-npm-install-and-npm-ci
Actual Behaviour
Because of the overarching use of npm install, it is not impossible that the local build differs from the build in the pipeline, due to dependency updates.
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Platform and Version
Archetype 31 and previous
Sample Code that illustrates the problem
see: https://github.com/eirslett/frontend-maven-plugin#running-npm Using the frontend-maven-plugin used in the archetype, it is possible to customize the arguments via the plugin configuration (install -> ci).
Logs taken while reproducing problem
This duplicates #685
Could this be closed then?