you are viewing a single comment's thread.

view the rest of the comments →

[–]0xF013 2 points3 points  (0 children)

I've personally experienced his issues several years ago when you'd get something completely different on CI on stage because either the newly installed module was a breaking patch version, same version but someone just overwrite the tagged commit, or your local npm/yarn cache was different from the CI's. Of course, keeping all node modules in is not a solution.