aem-project-archetype icon indicating copy to clipboard operation
aem-project-archetype copied to clipboard

Usage of 'npm ci' for Build Pipelines

Open gerrG1t opened this issue 3 years ago • 2 comments

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

gerrG1t avatar Nov 12 '21 07:11 gerrG1t

This duplicates #685

kwin avatar Feb 07 '22 22:02 kwin

Could this be closed then?

kevinolivar avatar Dec 21 '22 09:12 kevinolivar