We noticed that the cache created by the package-lock.json was never being used as the npm set-script commands alter the pacakge.json and the package-lock.json creating a different checksum. Adding the --no-save flag ensures it does not create a new package-lock.json
Jira Ticket ID:
What kind of change does this PR introduce? (check at least one)
[x] Bugfix (non-breaking change which fixes an issue)
[ ] Feature (non-breaking change which adds functionality)
[ ] Code style update
[ ] Refactor (refactoring or adding test which isn't a fix or add a feature)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Build-related changes
[ ] Other, please describe:
Does this PR introduce a breaking change? (check one)
[ ] Yes
[x] No
Did you test your solution?
[x] I lightly tested it in one browser
[ ] I deeply tested it in several browsers
[ ] I wrote tests around it (unit tests, integration tests, E2E tests)
We noticed that the cache created by the package-lock.json was never being used as the
npm set-script
commands alter the pacakge.json and the package-lock.json creating a different checksum. Adding the--no-save
flag ensures it does not create a new package-lock.jsonJira Ticket ID:
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
Did you test your solution?
Problem Description
Solution Description
Side Effects, Risks, Impact
Aditional comments: