Hi, considering that Sage 9 officially uses Yarn as dependency manager, why GitHub repository also track the
See this thread on Stack Overflow for further info.
Seems that the best approach is to track only the lock file used by the chosen dependency manager.
It’s not a big concern to update every time the
yarn.lock and the
package-lock.json to keep the consistency between the two lock files, but I don’t understand why I have to do this (useless) step.
As suggested in the linked thread, could I untrack and delete
package-lock.json from projects repositories in our company (we only use Yarn) or there is any reason to keep it updated and tracked?
Thank you all in advance for the feedback!