@atlowchemi/webfont-generator
v0.6.1
Published
Downloads
3,774
Readme
@atlowchemi/webfont-generator
A native Rust NAPI addon that generates webfonts (SVG, TTF, EOT, WOFF, WOFF2) and their companion CSS/HTML from a set of SVG icon files.
This is a ground-up rewrite of @vusion/webfonts-generator in Rust — the original package and its authors deserve credit for the API design and template system that this project builds on. The JS implementation is unmaintained, so this package reimplements the same pipeline natively for better performance and long-term maintainability.
The API is largely compatible with @vusion/webfonts-generator, with a few differences:
- The
cssContextandhtmlContextcallbacks receive only the context object. The original also passedoptionsand thehandlebarsinstance as additional arguments — those are no longer available. formatOptionsis now strictly typed as{ svg?: SvgFormatOptions; ttf?: TtfFormatOptions; woff?: WoffFormatOptions; woff2?: Woff2FormatOptions }. The original accepted arbitrary{ [format]: unknown }; theeotkey is no longer accepted (EOT is derived from the TTF output).- A new
optimizeOutputoption runs an SVG path optimizer over each glyph before assembling the font. Defaults tofalse; opt in for smaller output bytes at a small build-time cost. Also available asformatOptions.svg.optimizeOutput. formatOptions.woff2.compressionQualitysets the Brotli compression quality (0–11) for WOFF2 output. Defaults to11(smallest output); lower it (e.g. to10) for faster encoding at a marginal size cost.- A new
incrementaloption (defaultfalse) retains parsed glyph data on the result soresult.regenerateAsync(files, changes?)can rebuild after file changes without re-parsing the glyphs that didn't change or blocking the Node.js event loop. It refreshes the outputs in memory and, when the result was generated withwriteFiles, writes refreshed fonts to disk too while skipping unchanged CSS/HTML companion files. You pass the full file set (in the order a fresh build would use) plus what changed, or omitchangesto re-read/hash the full set and infer changes; the result is byte-identical to a freshgenerateWebfonts()of that set, additions included. - Generated font binaries (TTF, WOFF, etc.) may differ at the byte level because a different encoder is used, but the fonts are equally valid.
- CSS, HTML, and template output is identical.
Performance scales better with glyph count — for larger icon sets the native pipeline is significantly faster.
Incremental regeneration
let files = ['./icons/home.svg', './icons/search.svg'];
let result = await generateWebfonts({ files, dest, fontName: 'my-icons', incremental: true });
// On a watch event, rebuild reusing cached geometry for unchanged glyphs. Pass the full file set
// (in fresh-build order) so additions land in the right position, plus what changed:
result = await result.regenerateAsync(files, [{ path: './icons/home.svg', changeType: 'changed' }]);
// Or omit changes when watcher hints are unavailable/untrusted:
result = await result.regenerateAsync(files);
result.woff2; // refreshed bytesThe first argument is the complete file set after the change, in the order a fresh build would use (e.g. your glob result) — any file omitted from it is dropped. Each change is { path, changeType: 'added' | 'changed' | 'removed', name? }, where name is the resolved glyph name if you apply a custom rename; otherwise added files derive their name from the file stem, changed files keep their current name, and removed files ignore it. When changes is omitted or null, every current file is re-read and hashed to detect added/changed/removed paths automatically. regenerateAsync() returns a replacement result; the receiver stays readable and unchanged while work runs and after failure. Assign the replacement before starting another rebuild because overlapping calls from the same result lineage are rejected. Disk writes are not transactional. The synchronous, mutating regenerate() method remains available when blocking the event loop is acceptable. Results generated with cssContext or htmlContext callbacks cannot be regenerated because those JavaScript callbacks cannot be re-run during a rebuild.
Node.js (npm)
npm install @atlowchemi/webfont-generatorPre-built binaries are published for the following targets:
| Platform | Architecture | | -------------- | ----------------- | | macOS | x64, arm64 | | Linux (glibc) | x64, arm64, armv7 | | Linux (musl) | x64, arm64 | | Windows (MSVC) | x64, arm64 |
import { generateWebfonts } from '@atlowchemi/webfont-generator';
const result = await generateWebfonts({
files: ['./icons/home.svg', './icons/search.svg'],
dest: './dist/fonts',
fontName: 'my-icons',
types: ['woff2', 'woff'],
});
const css = result.generateCss();
const html = result.generateHtml();Rust library (crates.io)
cargo add webfont-generatoruse webfont_generator::{GenerateWebfontsOptions, FontType};
let result = webfont_generator::generate_sync(
GenerateWebfontsOptions {
dest: "dist/fonts".to_owned(),
files: vec!["icons/home.svg".to_owned(), "icons/search.svg".to_owned()],
font_name: Some("my-icons".to_owned()),
types: Some(vec![FontType::Woff2, FontType::Woff]),
..Default::default()
},
None,
).unwrap();
let css = result.generate_css_pure(None).unwrap();Async generation and incremental regeneration are available for Tokio applications. Async regeneration consumes the old result, preventing stale-result reuse, and returns the next result:
let result = result.regenerate_async(files.clone(), changes).await?;
// Or re-diff the complete file set:
let result = result.regenerate_all_async(files).await?;On failure, RegenerateError::into_result() recovers the consumed result for retry when the
blocking task returned normally. These consuming futures are not cancellation-safe: dropping one
does not stop already-started blocking work and the consumed result cannot be recovered.
CLI
The CLI is available as an opt-in feature (to avoid pulling in clap for library users):
cargo install webfont-generator --features cliUsage
webfont-generator [OPTIONS] --dest <DEST> <FILES>...Examples
# Generate default formats (eot, woff, woff2) from a directory of SVGs
webfont-generator --dest ./dist/fonts ./icons/
# Generate specific formats with a custom font name
webfont-generator --dest ./dist/fonts --types woff2,woff --font-name my-icons ./icons/
# Generate fonts with an HTML preview page
webfont-generator --dest ./dist/fonts --html ./icons/*.svgOptions
Arguments:
<FILES>... SVG files or directories containing SVG files
Options:
-d, --dest <DEST> Output directory
-n, --font-name <FONT_NAME> Font name [default: iconfont]
-t, --types <TYPES> Font types to generate [possible values: svg, ttf, eot, woff, woff2]
--css Generate CSS (default)
--no-css Skip CSS generation
--html Generate HTML preview
--no-html Skip HTML generation (default)
--css-template <CSS_TEMPLATE> Custom CSS template path
--html-template <HTML_TEMPLATE> Custom HTML template path
--css-fonts-url <CSS_FONTS_URL> CSS fonts URL prefix
--write Write output files to disk (default)
--no-write Do not write output files (dry run)
--ligature Enable ligatures (default)
--no-ligature Disable ligatures
--font-height <FONT_HEIGHT> Font height
--ascent <ASCENT> Ascent value
--descent <DESCENT> Descent value
--start-codepoint <START_CODEPOINT> Start codepoint (hex, e.g. 0xF101)
-h, --help Print help
-V, --version Print versionTemplates
Default CSS, SCSS, and HTML templates are available via the /templates export:
import { templates } from '@atlowchemi/webfont-generator/templates';
console.log(templates.css); // path to default CSS template
console.log(templates.scss); // path to default SCSS template
console.log(templates.html); // path to default HTML template