I think it was some regions in Cloudflare (in this case a European one) not having all of the static `vinext` JS files ready immediately at deploy time, and then a `404` on that region sticking around due to very aggressive cacheing.
I think it was some regions in Cloudflare (in this case a European one) not having all of the static `vinext` JS files ready immediately at deploy time, and then a `404` on that region sticking around due to very aggressive cacheing.