snabbdom-edge
Advanced tools
This package includes two functions, which useful for client-server applications built with snabbdom. Like the snabbdom this library is focused on simplicity, modularity, powerful features and performance.
This package implements next snabbdom modules:
The element properties module (snabbdom-edge/component/props.js) does not implemented here because properties exists exclusively on client-side.
On the server side you usually want produce HTML output from virtual nodes.
The writeHTML function does this thing for you.
The supported features includes attributes, style and class.
The another way to do this is using snabbdom-to-html package.
This package is a simple and clean alternative for it.
Typical usage:
TypeScript:
import {init as initHTMLWriter} from 'snabbdom-edge/write-html';
import {classModule} from 'snabbdom-edge/write-html/class';
import {styleModule} from 'snabbdom-edge/write-html/style';
import {datasetModule} from 'snabbdom-edge/write-html/dataset';
import {attributesModule} from 'snabbdom-edge/write-html/attributes';
// Init HTML render function with all available modules
const writeHTML = initHTMLWriter([
classModule, // makes it support toggled classes
// the props is only on client-side
styleModule, // handles styling on elements
datasetModule, // handles data-attributes
attributesModule // handles all other attributes
]);
// in request handler we generate virtual DOM
let vnode = render_tree();
// write HTML to response body directly to use lesser RAM
writeHTML(vnode, response);
// OR generate HTML string to write
const html = writeHTML(vnode);
response.write(html);
JavaScript:
// Init HTML render function with all available modules
var writeHTML = require('snabbdom-edge/write-html').init([
require('snabbdom-edge/write-html/class').default, // makes it support toggled classes
// the props is only on client-side
require('snabbdom-edge/write-html/style').default, // handles styling on elements
require('snabbdom-edge/write-html/dataset').default, // handles data-attributes
require('snabbdom-edge/write-html/attributes').default // handles all other attributes
]);
// in request handler we generate virtual DOM
var vnode = render_tree();
// write HTML to response body directly to use lesser RAM
writeHTML(vnode, response);
// OR generate HTML string to write
var html = writeHTML(vnode);
response.write(html);
On the client side you may read initial DOM before first patch when initializing your application.
The readDOM function does this thing.
This piece of code has been ported from snabbdom-virtualize with key differences:
html-entities package instead of DOM API calls.Usage example:
TypeScript:
import {init as initDOMReader} from 'snabbdom-edge/read-dom';
import {classModule} from 'snabbdom-edge/read-dom/class';
import {styleModule} from 'snabbdom-edge/read-dom/style';
import {datasetModule} from 'snabbdom-edge/read-dom/dataset';
import {attributesModule} from 'snabbdom-edge/read-dom/attributes';
// Init DOM reader function with all available modules
const readDOM = initDOMReader([
classModule, // makes it support toggled classes
// the props is only on client-side
styleModule, // handles styling on elements
datasetModule, // handles data-attributes
attributesModule() // handles all other attributes
]);
//before starting application on client
// we would like to read initial DOM
// now we can read global DOM node (i.e. <html>)
const _vnode = readDOM(document.documentElement);
// OR we can read only <body> as soon
const _vnode = readDOM(document.body);
// render the first virtual DOM
const vnode = render_tree();
// initiate the first patch
patch(_vnode, vnode);
JavaScript:
// Init DOM reader function with all available modules
var readDOM = require('snabbdom-edge/read-dom').init([
require('snabbdom-edge/read-dom/class'), // makes it support toggled classes
// the props is only on client-side
require('snabbdom-edge/read-dom/style'), // handles styling on elements
require('snabbdom-edge/read-dom/dataset'), // handles data-attributes
require('snabbdom-edge/read-dom/attributes')() // handles all other attributes
]);
//before starting application on client
// we would like to read initial DOM
// now we can read global DOM node (i.e. <html>)
var _vnode = readDOM(document.documentElement);
// OR we can read only <body> as soon
var _vnode = readDOM(document.body);
// render the first virtual DOM
var vnode = render_tree();
// initiate the first patch
patch(_vnode, vnode);
As you seen above the attributes module instantiated by calling as function. It implemented so in order to have possibility of transferring options to it. Available options is below:
attrs field.attrs field.attrs field.TypeScript:
import {init as initDOMReader} from 'snabbdom-edge/read-dom';
import {attributesModule} from 'snabbdom-edge/read-dom/attributes';
// Init DOM reader function with all available modules
const readDOM = initDOMReader([
attributesModule({ // handles all attributes
style: true,
class: true,
dataset: true
})
]);
JavaScript:
// Init DOM reader function with all available modules
const readDOM = require('snabbdom-edge/read-dom').init([
require('snabbdom-edge/read-dom/attributes').default({ // handles all attributes
style: true,
class: true,
dataset: true
})
]);
FAQs
The I/O for snabbdom (write HTML on server and read DOM on client).
We found that snabbdom-edge demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
/Security News
Socket identified 80 fake candidates targeting engineering roles, including suspected North Korean operators, exposing the new reality of hiring as a security function.
Application Security
/Research
/Security News
Socket detected multiple compromised CrowdStrike npm packages, continuing the "Shai-Hulud" supply chain attack that has now impacted nearly 500 packages.
Research
/Security News
Malicious update to @ctrl/tinycolor on npm is part of a supply-chain attack hitting 40+ packages across maintainers