Due low popularity of this project after all these years, and because I have shifted focus to better alternatives, this project is currently in maintenance mode, meaning that 100% feature parity with hyperHTML is not anymore an achievement, and only the simple/obvious will be fixed.
Among various changes happened to hyperHTML, the sparse attributes will likely not be supported, as the refactoring needed here would easily outperform the benefits.
As sparse attributes are never really been a must have, you can simply use attr=${...} and concatenate in there anything you want.
This is also true for most modern alternatives of mine, such as ucontent, but if that's the only deal breaker, have a look at heresy-ssr, which is 1:1 based on lighterhtml, hence likely always 100% in features parity with it, included sparse attributes.
hyperHTML lightness, ease, and performance, for the server.
Don't miss the viperHTML version of Hacker News
Live: https://viperhtml-164315.appspot.com/
Repo: https://github.com/WebReflection/viper-news
Similar to its browser side counterpart, viperHTML parses the template string once, decides what is an attribute, what is a callback, what is text and what is HTML, and any future call to the same render will only update parts of that string.
The result is a blazing fast template engine that makes templates and renders shareable between the client and the server.
No matter if you use ESM or CommonJS, you can use hypermorphic to load same features on both client and server.
// ESM example (assuming bundlers/ESM loaders in place)
import {bind, wire} from 'hypermorphic';
// CommonJS example
const {bind, wire} = require('hypermorphic');Both attributes and text nodes are safely escaped on each call.
const viperHTML = require('viperhtml');
var output = render => render`
<!-- attributes and callbacks are safe -->
<a
href="${a.href}"
onclick="${a.onclick}"
>
<!-- also text is always safe -->
${a.text}
<!-- use Arrays to opt-in HTML -->
<span>
${[a.html]}
</span>
</a>
`;
var a = {
text: 'Click "Me"',
html: '<strong>"HTML" Me</strong>',
href: 'https://github.com/WebReflection/viperHTML',
onclick: (e) => e.preventDefault()
};
// associate the link to an object of info
// or simply use viperHTML.wire();
var link = viperHTML.bind(a);
console.log(output(link).toString());The resulting output will be the following one:
<!-- attributes and callbacks are safe -->
<a
href="https://github.com/WebReflection/viperHTML"
onclick="return ((e) => e.preventDefault()).call(this, event)"
>
<!-- also text is always safe -->
Click "Me"
<!-- HTML goes in as it is -->
<span><strong>"HTML" Me</strong></span>
</a>const viperHTML = require('viperhtml');
function tick(render) {
return render`
<div>
<h1>Hello, world!</h1>
<h2>It is ${new Date().toLocaleTimeString()}.</h2>
</div>
`;
}
// for demo purpose only,
// stop showing tick result after 6 seconds
setTimeout(
clearInterval,
6000,
setInterval(
render => console.log(tick(render).toString()),
1000,
// On a browser, you'll need to bind
// the content to a generic DOM node.
// On the server, you can directly use a wire()
// which will produce an updated result each time
// it'll be used through a template literal
viperHTML.wire()
)
);Clients and servers inevitably have different needs, and the ability to serve chunks on demand, instead of a whole page at once, is once of these very important differences that wouldn't make much sense on the client side.
If your page content might arrive on demand and is asynchronous,
viperHTML offers an utility to both obtain performance boots,
and intercepts all chunks of layout, as soon as this is available.
Similar to a wire, viperHTML.async() returns a callback that must be invoked right before the template string,
optionally passing a callback that will be invoked per each available chunk of text, as soon as this is resolved.
// the view
const pageLayout = (render, model) =>
render`<!doctype html>
<html>
<head>${model.head}</head>
<body>${model.body}</body>
</html>`;
// the viper async render
const asyncRender = viperHTML.async();
// dummy server for one view only
require('http')
.createServer((req, res) => {
res.writeHead( 200, {
'Content-Type': 'text/html'
});
pageLayout(
// res.write(chunk) while resolved
asyncRender(chunk => res.write(chunk)),
// basic model example with async content
{
head: Promise.resolve({html: '<title>right away</title>'}),
body: new Promise(res => setTimeout(
res, 1000,
// either:
// {html: '<div>later on</div>'}
// ['<div>later on</div>']
// wire()'<div>later on</div>'
viperHTML.wire()`<div>later on</div>`
))
}
)
.then(() => res.end())
.catch(err => { console.error(err); res.end(); });
})
.listen(8000);Following a list of handy patterns to solve common issues.
True that, but if you follow a simple (render, model) convetion,
you can just have templates as html files.
<!-- template/tick.html -->
<div>
<h1>Hello, ${model.name}!</h1>
<h2>It is ${new Date().toLocaleTimeString()}.</h2>
</div>At this point, you can generate as many views as you want through the following step
#!/usr/bin/env bash
mkdir -p view
for f in $(ls template); do
echo 'module.exports = (render, model) => render`' > "view/${f:0:-4}js"
cat template/$f >> "view/${f:0:-4}js"
echo '`;' >> "view/${f:0:-4}js"
doneAs result, the folder view will now contain a tick.js file as such:
module.exports = (render, model) => render`
<!-- template/tick.html -->
<div>
<h1>Hello, ${model.name}!</h1>
<h2>It is ${new Date().toLocaleTimeString()}.</h2>
</div>
`;You can now use each view as modules.
const view = {
tick: require('./view/tick')
};
// show the result in console
console.log(view.tick(
viperHTML.wire(),
{name: 'user'}
));![greenkeeper[bot] avatar](https://avatars.githubusercontent.com/in/505?v=4 "greenkeeper[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent