DOM cache - my (almost) perfect server-side template library

I've been web programming for more than 30 years (how did that happen??) and I've just iterated again on how I do it.

I am now using server side DOM caching to allow me to write code like this:

const [feedQueryErr, feedQueryRes] = await pool.query(
        `select * from feed order by id desc`
).then(r=>[,r]).catch(e=>[e]);
if (feedQueryErr) {
     console.log("/ => feed query err:", feedQueryErr);
}

const page = await getJsdom("some-page");
page.body.parentElement
    .appendChild(page.createElement("script"))
    .textContent = `namePage("${feedName}");
feedsSet(${JSON.stringify(feedQueryRes.rows)});
posts(${JSON.stringify(postList)});`;
o.send(page.toString());

I find this to be a good trade off the things I like:

keep the HTML manipulation logic on the client side with templates or js
keep HTML hygiene on the server side, no string manipulation templates
no silly language in language like JSX either, I hate those because they just complicate editing
add the data description to the end of the page where all the main rendering has been done

I just made a package of my current implementation of this here at npm @nicferrier/dom-cache and this makes it even easier to use.

I'm a bit embarassed because it's such a tiny library and really all the credit, if there is any, goes to Andrea Giammarchi who made the library that makes this possible, linkedom. I note that he is looking for help with linkedom so if anyone reads this and thinks "I want to be an open source maintainer!" then please reach out to him.

Anyway, there we go, I think it's great coz it makes me faster.

fin