How did package-lock.json end up with sooo many changes?
Because I did a full update of it. Build was failing during the npm ci phase. Figured a refresh of the lock should help resolve that, which it did. If you'd rather it be done separately or more surgically, I don't mind, but in that case I'll pull that work out of this change.
Because I did a full update of it. Build was failing during the
npm ciphase. Figured a refresh of the lock should help resolve that, which it did. If you'd rather it be done separately or more surgically, I don't mind, but in that case I'll pull that work out of this change.