Skip to content

Clean up yarn.lock

Summary

yarn.lock is now hard to maintain as it has been updated for many months.

Improvements

Updating some package(s) requires changes in yarn.lock in general, but it tends to be time-consuming and/or error-prune.

Risks

Some conflicts between MRs might be occurred especially when clean up was done in a single MR. Split MRs might mitigate such conflicts.

Involved components

  • /package.json
  • yarn.lock

Optional: Intended side effects

Minor dependencies updates may cause some regressions but it is difficult to test everything by manual.

Optional: Missing test coverage

n/a

cf.

Some similar improvements:

Edited by 🤖 GitLab Bot 🤖