Can you spot which committed file explains this mismatch?

Estimated read time 1 min read

Post Contenthttps://www.youtube.com/shorts/ZGP1Fzc2Q_o

​ There is a small package management puzzle from a familiar workflow.
Plus local development and CI both install the same dependency, but they end up with different versions. Yet package.json has not changed.

The clue is in how the install is being resolved.

Watch the clip and share which file explains the mismatch.

Subscribe to Google for Developers → https://goo.gle/developers

Speakers: Christina Rafla   Read More Google for Developers 

You May Also Like

More From Author