he/him 
Users of JS source tooling (type checkers, linters, compilers, bundles), what do you dislike about existing solutions? Any features that you want but are impossible with existing tools?
-
I guess you could go as far as split at the "statement level" but I can't imagine a scenario why someone would want to do that.
You can automatically insert async boundaries (ie. import()) for code splitting if you can detect where it's safe and if the code isn't used in the critical path.
-
-
Oh so like a prepack kind of heuristic?
-
Technically any function which returns a promise can be code split if tooling can detect that pulling that func out makes sense.
- 4 more replies
New conversation -
-
-
Even when you have the full graph, do you think the critical path can be usefully approximated statically? A single dynamic condition ("if debug==true") could drastically change it.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.