Hey, amy
My thoughts were the same. So the first thing i did was to generate a preview env with a package-lock identical to the one that is in prod.
- Made sure lockfiles were 1-1
npm ci-ed- Pushed and created a preview env
Results were unfortunately the same 
I also considered the scenario that this is a vercel preview env issue. So i tried my luck and pushed to prod (that’s where the real testing happens anyhow), but unfortunately it was the same there. So i rolled-back