-
-
Notifications
You must be signed in to change notification settings - Fork 84
[RFC] Inline assets #16
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
Yep, that’s interesting :). Can you tell me more about how you would use the feature? Online everything? Or choose if you want to inline on an entry-by-entry basis? Or by filesize? |
I guess all of this. Somewhere need to inline everything, somewhere only js for page block but without vendor js. |
IMO inlining CSS can be very useful with "Critical CSS" technique - https://www.smashingmagazine.com/2015/08/understanding-critical-css/. |
Something like that required. We use inline assets with the custom extension now
this still works with Webpack 4 encore if option |
Btw, you could also iterator over the CSS or JS files via This feature is interesting - but I haven't researched it at all yet. I often look at what "native Webpack" does - an then try to stay as close to that as possible. |
Thank you for this issue. |
@weaverryan are you open for PR with |
What about option to inline assets (CSS or JS) into twig?
The text was updated successfully, but these errors were encountered: