one less thing to remember, we had discrepancies between versions from time to time
Timmy Willison
@timmywil
are the issues we had with package-lock.json still applicable? Also, what were they again? I recall a discrepancy between Windows and Mac.
although, choosing npm over yarn isn't necessarily something I want
Michał Gołębiowski-Owczarek
@mgol
yeah, that, plus from time to time the file was being changed when npm was updated
so it wasn't stable between npm versions
Timmy Willison
@timmywil
right
Michał Gołębiowski-Owczarek
@mgol
and people use different Node & npm versions so it was all pretty unstable
in my experience Yarn is way more stable with its lockfile format, for example
Timmy Willison
@timmywil
that's pretty much why I use yarn
Michał Gołębiowski-Owczarek
@mgol
me too :D
Timmy Willison
@timmywil
that everything?
Michał Gołębiowski-Owczarek
@mgol
plus, the thing between OSes is that e.g. fsevents is an optional package and only works on macOS so it's skipped on Windows. That means it doesn't get to package-lock when npm is run on Windows
so Windows-based contributors would be unable to update dependencies, etc.
@timmywil there's one PR where I need @gibson042's input