@resvg/resvg-wasm
Advanced tools
Changelog
[2.6.1] - 2024-03-25
Changelog
[2.6.1-beta.0] - 2024-03-11
This version solves the problem of missing DLLs caused by not installing Visual C++ Redistributable on Windows.
Changelog
[2.6.0] - 2023-10-20
🚀 Up to 115x faster for very large SVG files
Now resvg has been upgraded from v0.29.0 to v0.34.0, bringing with it a host of new SVG features and performance improvements.
Support SVG2 mask-type
property.
Allows quadratic Bézier curves: text might render slightly differently (better?). This is because TrueType fonts contain only quadratic curves and we were converting them to cubic before.
Clipping and masking is up to 20% faster.
Reduces the peak memory usages for SVGs with large paths (in terms of the number of segments).
A new rendering algorithm.<br>
When rendering isolated groups,
aka layers, we have to know the layer bounding box beforehand, which is ridiculously hard in SVG.<br>
Previously, resvg would simply use the canvas size for all the layers.
Meaning that to render a 10x10px layer on a 1000x1000px canvas, we would have to allocate and then blend
a 1000x1000px layer, which is just a waste of CPU cycles.<br>
The new rendering algorithm is able to calculate layer bounding boxes, which dramatically improves
performance when rendering a lot of tiny layers on a large canvas.<br>
Moreover, it makes performance more linear with a canvas size increase.<br>
The paris-30k.svg
sample from google/forma is rendered 115 times faster on M1 Pro now.
From ~33760ms down to ~290ms. 5269x3593px canvas.<br>
If we restrict the canvas to 1000x1000px, which would contain only the actual paris-30k.svg
content,
then we're 13 times faster. From ~3252ms down to ~253ms.
Changelog
[2.5.0] - 2023-10-16
Now we can finally loading custom fonts in Wasm, including the WOFF2 format (see playground), thanks to the high-performance woff2-rs
.
In addition, we implemented smarter default font family fallback. the defaultFontFamily
option can now be omitted. We'll read the font-family from the incoming fonts and set it to the default.
<script src="https://unpkg.com/@resvg/resvg-wasm"></script>
<script>
;(async function () {
await resvg.initWasm(fetch('https://unpkg.com/@resvg/resvg-wasm/index_bg.wasm'))
const font = await fetch('./fonts/Pacifico-Regular.woff2')
if (!font.ok) return
const fontData = await font.arrayBuffer()
const buffer = new Uint8Array(fontData)
const opts = {
font: {
fontBuffers: [buffer], // New in 2.5.0, loading custom fonts.
// defaultFontFamily: 'Pacifico', // You can omit this.
},
}
const svg = '<svg> ... </svg>' // Input SVG, String or Uint8Array
const resvgJS = new resvg.Resvg(svg, opts)
const pngData = resvgJS.render(svg, opts) // Output PNG data, Uint8Array
const pngBuffer = pngData.asPng()
const svgURL = URL.createObjectURL(new Blob([pngData], { type: 'image/png' }))
document.getElementById('output').src = svgURL
})()
</script>
fontBuffers
option. Thanks to @antmelnyk #217We have improved the upstream svgtypes#14, allow parsing of float rgb()/rgba()
values from CSS Color 4 draft like rgb(3.14, 110, 201)
.
Changelog
[2.4.0] - 2023-02-09
This is a brand new version with 2-3x faster performance. It also resolves an issue with a specific SVG causing an error, and all users are advised to upgrade to this version.
resvg-js(Rust):
39.6 ops/s, ±1.72% | fastest
sharp:
10.9 ops/s, ±31.43% | 72.47% slower
svg2img(canvg + node-canvas):
10.8 ops/s, ±28.52% | slowest, 72.73% slower
The upgrade will be hard due to the big changes made to upstream resvg. resvg 0.28.0 started with the removal of the ability to output SVG string, and we had to backport that functionality to a new crate: usvg-writer
.
Eventually, we upgraded resvg for 2 successive versions, and are now at the latest 0.29.0.
fix: 'the previous segment must be M/L/C' error. #204 Thanks to @yisibl
This is a normal error thrown by resvg when parsing Path Command and has been confirmed as fixed in resvg 0.30.0(see commit).
Add a test to ensure it is now fixed.
thread 'main' panicked at 'the previous segment must be M/L/C', usvg/src/pathdata.rs:219:17
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
fatal runtime error: failed to initiate panic, error 5
Changelog
[2.3.0] - 2023-02-02
fix: update napi-rs(2.10.13) to resolve Electron 21+ create Buffer issues. #195
Electron 21 and later will have the V8 Memory Cage enabled, with implications for some native modules. https://www.electronjs.org/blog/v8-memory-cage
This means that all napi-rs-based native modules will be affected. Usually there is an error like this:
UnhandledPromiseRejectionWarning: Error: Failed to create napi buffer
Good thing napi-rs has implemented a compatible approach in the new version, thanks to @Brooooooklyn's work.
feat: add wasm file to exports. Thanks to @hadeeb #186
This solves the problem that direct require.resolve("@resvg/resvg-wasm/index_bg.wasm")
in tools like vite or webpack would report an error.
Module not found: Package path ./index_bg.wasm is not exported from package
/playground/node_modules/@resvg/resvg-wasm (see exports field in
/playground/node_modules/@resvg/resvg-wasm/package.json)
See the Node.js documentation for details about why:
Existing packages introducing the "exports" field will prevent consumers of the package from using any entry points that are not defined,
fix(ci): use zig to cross-compile armv7. #176
This solves the problem of CI errors:
Error: /lib/arm-linux-gnueabihf/libm.so.6: version `GLIBC_2.35' not found (required by /build/resvgjs.linux-arm-gnueabihf.node)
Due to the GitHub Actions Ubuntu upgrade from 20.04 to 22.04, the glibc version became 2.35. To maintain our compatibility, zig cross-compilation is now enabled to support older versions of glibc systems.
| Distribution | Glibc | GCC | | ---------------- | ----- | ------ | | CentOS 7 | 2.17 | 4.8.5 | | Ubuntu 16.04 | 2.23 | 5.4.0 | | Ubuntu 18.04 | 2.27 | 7.5.0 | | Ubuntu 20.04 | 2.31 | 9.4.0 | | Ubuntu 22.04 | 2.35 | 11.2.0 | | Debian 10.12 | 2.28 | 8.3.0 | | Debian 11.4 | 2.31 | 10.2.1 |
doc: add Node.js 18 to 'Support matrix'. #155
Changelog
[2.2.0] - 2022-11-18
Now resvg-js can be run natively (not Wasm) directly in Deno, this allows to get close to the performance of Node.js native addons in Deno.
deno run --unstable --allow-read --allow-write --allow-ffi example/index-deno.js
See Deno Example
import * as path from 'https://deno.land/std@0.159.0/path/mod.ts'
import { Resvg } from 'npm:@resvg/resvg-js'
const __dirname = path.dirname(path.fromFileUrl(import.meta.url))
const svg = await Deno.readFile(path.join(__dirname, './text.svg'))
const resvg = new Resvg(svg, opts)
const pngData = resvg.render()
const pngBuffer = pngData.asPng()
await Deno.writeFile(path.join(__dirname, './text-out-deno.png'), pngBuffer)
In addition, resvg-js can return the raw pixels data of the PNG, which can be very convenient for scenes where only pixels need to be processed.
.pixels()
API for returning PNG pixels data (#123).paint-order
attribute support. Markers can only be under or above the shape.writing-mode
variants vertical-rl
and vertical-lr
. Thanks to @yisibl.dpi
option is not the DPI in the PNG file. (#146)infer
crate, this reduced the size of the Wasm file by about 4.3%. (#165)
png
crate in renovate.json
. (by @CGQAQ in #161)