Built-ins & Utilities

uuidv4

const id = uuidv4();

Buffer

For Buffer types, import type declarations from breeze-plugin-kit so tsserver does not infer Node.js / DOM types incorrectly:

import type { Buffer } from "breeze-plugin-kit";

Breeze injects a Node.js-compatible Buffer subset, not a browser ArrayBuffer wrapper.

Buffer.from(data, encoding?)
Buffer.alloc(size)
Buffer.isBuffer(obj)
Buffer.byteLength(string, encoding?)

path

Path utilities, compatible with a Node.js path subset.

path.join("/a", "b", "../c"); // "/a/c"
path.resolve("a", "b"); // absolute path
path.dirname("/a/b/c.txt"); // "/a/b"
path.basename("/a/b/c.txt"); // "c.txt"
path.extname("/a/b/c.txt"); // ".txt"

TextEncoder / TextDecoder

UTF-8 encode/decode.

const bytes = new TextEncoder().encode("hello");
const text = new TextDecoder().decode(bytes);

structuredClone

const copy = structuredClone({ a: 1, b: [2, 3] });

Base64

Two global helpers for Base64 encode/decode:

const bytes = bytesFromBase64("aGVsbG8="); // Uint8Array
const text = bytesToBase64(new TextEncoder().encode("hello")); // "aGVsbG8="

breeze-plugin-kit also exports the same names and types; prefer importing from the package:

import { bytesToBase64, bytesFromBase64 } from "breeze-plugin-kit";

Often used with crypto: decrypt to Uint8Array, then bytesToBase64 for a string.

hostCrypto and __web

Besides mounting crypto on globalThis.crypto, the runtime also exposes:

• hostCrypto — same object as crypto, fallback access path
• __web — internal runtime bus with all injected capabilities (fs, path, native, bridge, base64, crypto, uuidv4, etc.)

Prefer not to use __web directly; its fs does not exist on real Breeze hosts. Use breeze-plugin-kit wrappers or named globals (bridge, native, BreezeHtml, etc.).