Perhaps surprising: I agree with @slightlylate that the discussion we're having about web performance isn't helping us move forward as a community.
-
-
Another piece is figuring out how to model async fetching in frameworks so that simply using popular routers in the normal way gets you a decent amount of code splitting.
-
import() is a nice primitive, but asking every dev to use it manually is asking people to deprioritize it. It's great that the tooling is getting support that we can use in frameworks.
-
That’ll always be tricky. Maybe some Babel plugin that takes <Route> <Component> and rewrites it using an async middle man? Tough to get right.
-
There's already in-framework async points inside of the routing layer. The framework can take one of those points and automatically fetch code associated with a route using import() and some registry or naming convention.
End of conversation
New conversation -
-
-
Getting that fixed, and teaching devs how to use import() would fix a solid 80% of these issues, minimum.
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.


