@aduh95/viz.js
Advanced tools
Changelog
@aduh95/Viz.js v3.0.0 (2020-05-27)
Viz.prototype.renderSVGElement
. You can use
renderString
and DOMParser
to achieve the same result.Viz.prototype.renderImageElement
. You can use
renderString
and Canvas
to achieve the same result.Module
and render
from Viz
constructor's options
(you must now specify either worker
or workerURL
).full.render.js
script is replaced by the render.node.mjs
and render.browser.js
modules.render.node.js
module (that replaces full.render.js
)
exports a worker_thread factory when imported from the main thread. It's
available through @aduh95/viz.js/worker
specifier on Node.js and bundle
tools that support package.json
#exports
.render.browser.js
module (that replaces full.render.js
)
exports a function which takes a Module object as parameter. You should use it
to give the path to render.wasm
the Emscripten script. You should not import
this module from the main thread. On bundle tools that support
package.json
#exports
, you can use the specifier @aduh95/viz.js/worker
.render.js
file like asm.js used to. Depending on your bundling tool, you may
need some extra config to make everything work. You might also use the
synchronous API, which bundles the asm.js code, although its usage should be
strictly limited to Node.js or webworker use.require('@aduh95/viz.js')
returns now a
Promise<Viz>
.require('@aduh95/viz.js')
is deprecated, use
import('@aduh95/viz.js')
instead.worker_threads
.viz.c
to C++ to use
Emscripten's Embind.ALLOW_MEMORY_GROW
compiler option to avoid failing on large graphs.@aduh95/viz.js/sync
).@aduh95/viz.js/async
).