Unused CSS preload
See original GitHub issueI’ve only just started getting this problem with a new nextjs app, where css files aren’t preloaded, and therefore not used at all:
A preload for 'https://*******.vercel.app/_next/static/css/db098983a22a0aa338df.css' is found, but is not used because the request credentials mode does not match. Consider taking a look at crossorigin attribute.
I’m using sass modules, and this is with nextjs 9.5.3 and webpack 5 (but the same issue occurs with webpack 4). Any ideas?
_Originally posted by @howells in https://github.com/vercel/next.js/discussions/16850_
Issue Analytics
- State:
- Created 3 years ago
- Reactions:19
- Comments:20 (4 by maintainers)
Top Results From Across the Web
Http/2 preloaded css is not applied and considered unused
The resource http://localhost:8080/core.css was preloaded using link preload but not used within a few seconds from the window's load event.
Read more >Remove Unused CSS - WP Rocket Knowledge Base
Clear the cache of the URL and preload that if the "Preload" feature is active. Remove all stylesheets and inline CSS from the...
Read more >preload key requests and unused css - WordPress.org
Hi, I launched pagespeed. Pagespeed gives me a problem with preload key requests on the woff font. It also tells me that I...
Read more >How to Inline Critical CSS and Defer Unused CSS in WordPress
Preload plays a helpful role especially in solving LCP issues of images and fonts. To remove the “Preload Key Requests” flag, Pagespeed Insights ......
Read more >Remove unused CSS - Chrome Developers
Learn about the unused-css-rules audit. ... Then load the rest of the styles asynchronously using the preload link.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
same on
"next": "^10.0.0",
Any update on this issue or workaround? I’m experiencing the same problem.