-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better cache busting #1109
Comments
vercel deploys would fix this plobably |
I'm sure there's an elegant solution that wouldn't require using vercel. I would rather we go for a simple fix for this issue |
yeah, i just maintain that vercel would give us lots of other nice benefits too |
as vercel want me to think obviously so they can make their investors happy but its free so |
I think I've found one of the issues... /api/compiler is returning a 304. Once I manually loaded this endpoint, I stopped getting errors. adding the backend tag too |
I think |
When we update certain things like the recent #1103 , it breaks the site because the browser cache doesn't play well with the new state of things
The text was updated successfully, but these errors were encountered: