WIP: demo of using rollup code splitting prototype rule#76
WIP: demo of using rollup code splitting prototype rule#76gregmagolan wants to merge 6 commits intoangular:masterfrom gregmagolan:rollup-code-splitting
Conversation
|
If I understand right from the bazel rule in here, it is hardcoded to know about the entry point for the lazy loaded foo module. I recently also used rollup to create a working set of lazy bundles, with that same manual gathering of the entry points. I'm really looking forward to seeing something to gather them automatically - from some chat discussion it sounds like the "official" way to do this could take a few months to come through. |
|
@kylecordes Yes. This is an early prototype for this and the entry points are hard-coded in the rule and in index.html. |
|
Igor and I have been working here: in an earlier snapshot, there was an Longer-term we should get them from a static analysis output from individual libraries. |
src/index.html
Outdated
| this JS resource would be served from a static file. | ||
| <script src="/system.js"></script> | ||
|
|
||
| <script> |
There was a problem hiding this comment.
looks like this script could easily be another output of the rollup_bundle rule, placed in the runfiles.transitive_files so it's available to be loaded by anything with a transitive data[] dep
|
Seems like some files are not git add'ed? Where's the change in |
|
@gregmagolan @alexeagle Thanks - I will keep an eye on that PR and any successors, and try to provide a bit of testing-with-code-out-here-in-the-wild where feasible. |
@alexeagle You mean the one in here? https://github.com/bazelbuild/rules_nodejs/pull/104/files :) |
|
Closing this PR since we don't plan to merge right now, the primary copy of this code is in Greg's fork |
No description provided.