[docs] Fix docs using wrong service worker

[cherniavskii]

See mui/material-ui#36808 (comment)

[mui-bot]

Netlify deploy preview

Netlify deploy preview: https://deploy-preview-9030--material-ui-x.netlify.app/

Updated pages

No updates.

These are the results for the performance tests:

Test case	Unit	Min	Max	Median	Mean	σ
Filter 100k rows	ms	619	1,007.5	638.3	785.16	165.178
Sort 100k rows	ms	637.8	1,079.6	922.7	917.46	149.543
Select 100k rows	ms	220.3	366	275.4	293.12	61.537
Deselect 100k rows	ms	129.2	323.4	215.7	229.52	79.279

Generated by 🚫 dangerJS against 83086a7

[cherniavskii]

I removed this line just for testing purposes in the deploy preview.
Looks good:

I'll revert this change

[LukasTy]

❤️ 💯

[oliviertassinari]

I'm not sure about my suggestion in hindsight. Does it mean that we will have two service workers trying to serve the https://mui.com/x/* pages? I have tried to dive a bit deeper into how the scope works for service workers, e.g. scope in https://developer.mozilla.org/en-US/docs/Web/API/ServiceWorkerContainer/register.

If our goal is to entirely get rid of the sw.js logic, then maybe should revert this PR, remove the sw logic from this repo as it would become dead code, and apply #8598 in the docs-infra codebase (in https://github.com/mui/material-ui to be clear). I think it's what was proposed in

mui/material-ui#36808 (comment)

[cherniavskii]

@oliviertassinari I decided to try out the no-op service worker on a smaller scale first to ensure it works as expected.
As far as I can tell, it's working great - I cannot reproduce the issues described in mui/material-ui#36808 on MUI X docs https://mui.com/x/introduction/. I couldn't get a single outdated page 🎉

I would give it a bit more time to make sure the approach indeed works as expected, and then we can replace the service worker in the core repo as well 👍

[oliviertassinari]

From what I can observe, we do get both SW installed & activated but only the SW of the narrowest scope handles the requests. Nice 👍