Ability to prevent preloading client-side scripts in next/document's Head #16853
Comments
|
Thank you! That was quick |
|
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Feature request
Is your feature request related to a problem? Please describe.
Occasionally, I want to omit all client-side JavaScript on certain pages. I still want to be able to use JSX components to render the HTML (either via static export or SSR), but I don't want to hydrate the app on the client at all.
So I write a custom
Documentthat conditionally omits the<NextScript />element for certain pages.But when I do this, the default
<Head />still renders various<link rel="preload">links for various JS files. So the scripts are still downloaded even though they are never executed, wasting bandwidth.Describe the solution you'd like
The ability to disable preload links by setting a prop on the
Headcomponent fromnext/document.Describe alternatives you've considered
I could omit the
<Head />entirely and write my own<head>...</head>, omitting preload link elements, but that would mean losing the other functionality ofHead.Maybe the official
Headcould include some magic that automatically preventslink[rel=preload]elements being rendered if the parentDocumentdoesn't also include a<NextScript />. That might sound a bit clever, but maybe it's the right approach logically.The text was updated successfully, but these errors were encountered: