Lazy loading compatibility
See original GitHub issueDoes the use of <i18n>
blocks inside of components defeat the point of lazy loading? Or does webpack handle this some how even though the strings aren’t stored in separate files before build?
Issue Analytics
- State:
- Created 5 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Lazy loading via attribute for images & iframes - CanIUse
1 Firefox only supports lazy loading for images ; 2 Can be enabled in Settings under the Safari > Advanced > Experimental Features...
Read more >Browser-level image lazy loading for the web - web.dev
Browser-level support for lazy loading images is now supported on the web! This video shows a demo of the feature: In Chrome 76...
Read more >Cross Browser Compatibility of Lazy loading via attribute for ...
Lazy loading via attribute for images & iframes is Not Supported on Safari 14, which means that any user who'd be accessing your...
Read more >Lazy loading - Web performance | MDN
Lazy loading is a strategy to identify resources as non-blocking (non-critical) and load these only when needed. It's a way to shorten the ......
Read more >Native Lazy Loading - CSS-Tricks
The loading attribute allows a browser to defer loading offscreen images and iframes until users scroll near them. loading supports three values ......
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
@kazupon I have some doubts about it. Is the component lazy loaded at all with all i18n strings or just the user selected locale messages?
I really like the approach of this library, but if I have for example 3 locales with 10 translated messages it, all the 30 translated messages will be loaded inside the js file? Or somehow can we handle and load this translation messages separated to only load those 10 that is from the user’s selected locale?
@kazupon I’m also interested on this functionality, I want to lazy load the json files declared on
<i18n>
block (separated chunks for every block).