Size · tinyaml

Bundle size, KiB gzip

Each entry as npm ships it in dist/, bundled with esbuild, minified ESM, then gzip -9, from scripts/size.ts. A KiB is 1,024 bytes. Gzip sizes come from the zlib in the official Node builds; a Node linked to another zlib, such as Homebrew's, gives about 1% less.

All sizes

Section titled "All sizes"

Entry	Minified	Gzip
`tinyaml`	17.3 KiB	7.8 KiB
`tinyaml/js-yaml`	26.3 KiB	11.7 KiB
js-yaml 4	42.8 KiB	14.4 KiB
`tinyaml/js-yaml-v5`	39.0 KiB	16.0 KiB
js-yaml 5	56.4 KiB	17.1 KiB
`tinyaml/yaml`	39.2 KiB	16.8 KiB
yaml	95.8 KiB	29.9 KiB
`tinyaml/yamljs`	17.7 KiB	8.0 KiB
yamljs	28.4 KiB	8.8 KiB
`tinyaml/std`	24.5 KiB	10.7 KiB
@std/yaml	35.4 KiB	11.3 KiB

The tinyaml entries export everything in the subpath. js-yaml 4 and yamljs are bundled whole, js-yaml 5 with load, loadAll, dump, Schema and YAMLException, yaml with only parse and stringify, and @std/yaml with parse, parseAll and stringify.

The parser is one pass over character codes that builds JS values directly, with no tokens or syntax tree in between. Every entry shares it, so a subpath only adds its own value rules, error messages and stringifier. Each entry is built with the branches of one parser mode only: the spec for the root and tinyaml/yaml, js-yaml 4's leniency for tinyaml/js-yaml, tinyaml/yamljs and tinyaml/std, and js-yaml 5's rules for tinyaml/js-yaml-v5, each with only its own engine's settings. scripts/size.ts fails if an entry still holds another mode's code. The parser reports errors as numbered codes, and each entry has its own table of wording, so no bundle carries another library's messages.