Clicking on this should work: Top left nav >> components
Page shows dark mode on my macbook pro 15 inch.
Go to https://material-ui.com/
Click on this. Doesn't work: Top left nav >> components
Page does not show dark mode.
Using older versions of the site works. e.g. https://v4-10-2.material-ui.com/
@keven425 Please could you (or one of the brigade ๐) let us know more specifically which page doesn't work in dark mode or how to reproduce it? I can't reproduce the issue here.
Seems like our main bundle is not loaded at the moment. https://material-ui.com/ attempts to load https://material-ui.com/_next/static/runtime/main-89979d2bf3276e7cc85c.js which returns a 404. The side is therefore not interactive.
Same issue - search also not showing up and demos are not clickable.
Might be a CDN edge problem, as https://material-ui.com/_next/static/runtime/main-89979d2bf3276e7cc85c.js is fine for me...
Edit: I've triggered a fresh deploy - let's see if it helps.
Might be a CDN edge problem, as material-ui.com/_next/static/runtime/main-89979d2bf3276e7cc85c.js is fine for me...
Seems like it. It's fine for
netlify.app: https://latest--material-ui-docs.netlify.app/_next/static/runtime/main-89979d2bf3276e7cc85c.js
but not for
material-ui.com: https://material-ui.com/_next/static/runtime/main-89979d2bf3276e7cc85c.js
Somebody needs to fix the "Internet" ๐ Update: My "Internet" is fixed.
Strange, it works on Firefox and Safari but fails on Chrome and Edge.
It now fully works (tested on Chrome, Firefox, and Safari) and the page doesn't have any huge big issues. I think that this can be closed now.
(Note: it's now broken again, but it worked for around 4 minutes).
It's still an issue. Using the chromium based edge

It seems to be an issue with Netlify: https://community.netlify.com/t/one-deployed-to-main-domain-random-assets-404/24519/.
I'm having that issue too. I've tried Chrome, Edge, Firefox.
It's not working, 404 in the next bundle
It's working now for me. Anyone else still experiencing issues?
It's working now!
Closing since this particular incident seems to be resolved. Sorry for the inconvenience.
The issue seems resolved. I have reverted https://github.com/mui-org/material-ui-docs/commit/a7fa7aa97bb8c8b0fcbef4269d7153b81673c540. The rational from Netlify's team is:
There's a rewrite configured which points to a non-production deploy. [โฆ] TL:DR; the rewrite to the release-- branch is unpredictable and not something our team advise!
@oliviertassinari From the description, it seems like https://github.com/mui-org/material-ui-docs/commit/a7fa7aa97bb8c8b0fcbef4269d7153b81673c540 was intended to fix the issue that reverting it is also intended to resolve? If so, what's the root cause of the issue that led to this change in the first place?
@mbrookes The initial issue I was trying to solve is similar: the proxy was linking a non-production env as well as a wrong version (v5 instead of v4). I fixed the rewrite rule to point to v4 and a production env but the returned content by Netlify was still wrong after 1-hour post-deployment. I was hoping https://github.com/mui-org/material-ui-docs/commit/a7fa7aa97bb8c8b0fcbef4269d7153b81673c540 would invalidate the cache.
Most helpful comment
It seems to be an issue with Netlify: https://community.netlify.com/t/one-deployed-to-main-domain-random-assets-404/24519/.