Hydration mismatch errors only in production deployment, not when running locally with same code/env

[danthegoodman1]

When running in our EKS cluster, I see the following errors in the console:

The problem is, when running the exact same npm run build && npm start in my local environment, using the exact same env vars, I do not get these issues. I don't get them with npm run dev either, so I'm unable to recreate anywhere but the hosted env.

I also do not get this on our hosted staging env, which is running the same code. There's nothing special about our production environment vs what I have set up locally, everything is pixel-for-pixel the same on each page between my two browser tabs.

How can I enable more helpful errors messages with the production build, or go about debugging this?

[danthegoodman1]

My issue ended up being a toLocaleString that didn't pin the timeZone, and our staging env didn't hit the condition where it showed me that data, so I was able to reverse engineer that pretty quick.