This seems like a caching issue. I noticed that our webpack config for the client/src/client (workers, frame-runner, etc) do not create a hashed binary. A recent PR seems to have updated the enzyme package. But webpack builds a non-hashed version '[name].js' instead of '[name].[hash].js'
Our CDN caching aggressively caches JavaScript and this is the root cause. As an immediate fix I have invalidated our cache, which means a perf hit to us.
But the real issue is we need to see why webpack is behaving like it is. Can someone please report a GitHub issue for tracebility and add it here in comments.
Thanks.