@Punam -- this is still valid. Right now, our in-content web-pages is all bundled. The idea here is that once omnijar caching for local content ES modules is sufficiently good, it's conceivable (though not clear how likely) that we could simply stop bundling entirely (or partly) and load the es modules we use directly (possibly some of them lazily), and performance could be good enough. It's not particularly clear that this is likely, so I suspect the first steps here would be to: * figure out approximately what this would look like (eg how many files, particularly at startup time) * do a very simple, very-time-boxed prototype * if we hit the time-box, find the right person in the JS team or elsewhere to give us a sense of whether this is worth prototyping further. Adding a few folks to the CC (Hi, Mark & Gijs) who might have some sense of this off the top of their heads.
Bug 1459770 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
@Punam -- this is still valid. Right now, our in-content web-pages are all bundled with webpack. The idea here is that once omnijar caching for local content ES modules is sufficiently good, it's conceivable (though not clear how likely) that we could simply stop bundling entirely (or partly) and load the es modules we use directly (possibly some of them lazily), and performance could be good enough. It's not particularly clear that this is likely, so I suspect the first steps here would be to: * figure out approximately what this would look like (eg how many files, particularly at startup time) * do a very simple, very-time-boxed prototype * if we hit the time-box, find the right person in the JS team or elsewhere to give us a sense of whether this is worth prototyping further. Adding a few folks to the CC (Hi, Mark & Gijs) who might have some sense of this off the top of their heads.