Views
Opened this issue · 3 comments
Extract the view engine abstraction from express to here.
(Work is underway)
i intended https://github.com/expressjs/templation to be it, but it's not backwards compatible. specifically, i'd like the next framework to not have req.next and res.next. it's up to you guys on this.
but i don't want to use consolidate.js anymore. we can start maintaining it, but i'd still like streaming support and have each adapter be a separate file as a getter like templation, so it'll essentially be a rewrite anyways.
That stuff can all be considered for future releases.
Right now everything just kind of a modularized port of 4.8.x so that user migration can be easy. :)
specifically, i'd like the next framework to not have req.next and res.next
yes, there are a lot of things we would like to shed :)
but i don't want to use consolidate.js anymore. we can start maintaining it, but i'd still like streaming support and have each adapter be a separate file as a getter like templation, so it'll essentially be a rewrite anyways.
yep. and in fact, i had thought about it, and really, for views and router the majors would just contain out "optimum general purpose" one; if we rewrite it, we can then always publish the old version into a new package if people really want to continue to use it without using an old version of the module (i.e. because they wanted to use the old and new at the same time).
but yea, we want to capture the expressjs crowd at first with compatible stuff, then move from there to better/cooler things :) we can then always re-publish later with "express" in the module name, lol