Can you spot which committed file explains this mismatch?

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

Leave a Reply

Your email address will not be published. Required fields are marked *

Scroll to Top