Closed sebastiaanspeck closed 1 year ago
Hmm... The yarn.lock file isn't supposed to stay locked until we perform a yarn update? Like with npm? I have the impression that it re writes following a yarn install in BudgetInstall.php
After running yarn install
it doesn't update, but when using npm install
it does update
It's seem to be a know issue https://github.com/npm/cli/issues/5126 on npm
So the fix for now is to use yarn
over npm
Someone say
I mean, the workaround is just to restore the file with git restore yarn.lock after npm is run, but it gets boring.
We can maybe add on budgetinstall this restore if we select npm as package manager ?
Sounds like a good idea
See https://github.com/sebastiaanspeck/budget/commit/0d5aaef08845224d242e4ca72b30bee1a9699cb5 for the contents. Maybe we/you need to update the dependencies (and update composer as well)?