-
-
Notifications
You must be signed in to change notification settings - Fork 384
link=preload support #142
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
Comments
I have this issue also. Latest lighthouse test recommends as such: Did you find a solution @Medsestrun |
I met this and using preload-webpack-plugin resolved it in my case. |
Any update on this? I might be missing something and this is already possible, but if this is possible to achieve, it would be a very nice feature to have. And if it's possible without having to include other packages, that would be even better. |
Would love support for this. |
preload-webpack-plugin is nice but will only work in tandem with html-webpack-plugin. My case is server-side rendering and I have no idea how to do it yet. |
I’ll built this soon under. https://github.com/ScriptedAlchemy/webpack-external-import Of course contributions are welcome |
For those who are still waiting, there is workaround for mini-css-extract-plugin > 1.2.0 :
|
Hey @mikelpro, thank you for your solution. It works!
|
Because rel="preload" just tells browser which resource should be available as soon as it is required for the rendering(like priority) and rel="stylesheet" actually loads this resource |
Hi guys, I'm using the razzle after js boilerplate and have been running into the preload key requests when trying to improve optimization, I'm using uglifyjs and mini css extract plugin and have added the above fix to my razzle.config file new MiniCssExtractPlugin({ However I'm not able to see where the preloaded chunks are being injected into the head, I only see the initial rel="stylesheet" I'm using:
Am I missing something in my configuration? |
@Kirsten1996 it doesn't work for me as well. Looks like the |
No description provided.
The text was updated successfully, but these errors were encountered: