Replies: 3 comments
-
Exactly, and I think I can have streaming support even in a MVP (it's a must have, and is architecturally structuring).
That also was my though on this whole endeavor. If (when) we ever need ponyfills, we should add them in dedicated repos only to limit bloat and perf impact. And I don't think we'll need utils libs, at least not for now. |
Beta Was this translation helpful? Give feedback.
-
MVP done in vikejs/bati#259 I'll extract the necessary information in dedicated discussions. |
Beta Was this translation helpful? Give feedback.
-
I wonder what an MVP could look like.
If we skip support for HTML Streaming for now, maybe there is a way to have an MVP that is fairly simple (e.g. that doesn't use any mutation observing) and that already works for Bati. I'm guessing for Bati for now we only need two universal handlers (Vike + Telefunc) and one universal middleware (Authentication).
(Although HTML Streaming is quite essential, especially for React, but maybe there is an easy way to support streams: in principle it should be enough if Universal Handler merely passes the stream around and doesn't need to manipulate the stream itself.)
For example, we don't need order magic numbers for now, and I guess we don't need universal Express.js middlewares to support Bati's use case.
Maybe the MVP could even have zero-dependencies. Maybe we can build on top of a lean core.
(It's neat to have discussions and experimentations to minimize blind spots and minimize slowing-down surprises down the line.)
Beta Was this translation helpful? Give feedback.
All reactions