Can you spot which committed file explains this mismatch?

Author: Google for Developers - Bewertung: 0x - Views:23

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