YAML load/dump with a runtime-selected backend. The JVM artifact ships YAMLStar; Babashka uses its bundled clj-yaml.
Preference order on the JVM:
Under babashka only clj-yaml is used: it ships built into bb, while yamlstar
does not load under bb's SCI. Both backends receive JSON-shaped data (string
keys, no keywords — see bridge.io/yaml-stringify) and dump in block style, so
on-disk YAML is byte-stable across runtimes.
YAML load/dump with a runtime-selected backend. The JVM artifact ships YAMLStar; Babashka uses its bundled clj-yaml. Preference order on the JVM: 1. yamlstar — pure YAML 1.2, reflection-free, GraalVM native-image friendly; 2. clj-yaml (SnakeYAML). Under babashka only clj-yaml is used: it ships built into bb, while yamlstar does not load under bb's SCI. Both backends receive JSON-shaped data (string keys, no keywords — see `bridge.io/yaml-stringify`) and dump in block style, so on-disk YAML is byte-stable across runtimes.
(dump data)Serialize data (JSON-shaped: string keys, no keywords) to a YAML string.
Serialize `data` (JSON-shaped: string keys, no keywords) to a YAML string.
(load s)Parse a YAML string into Clojure data with string keys.
Parse a YAML string into Clojure data with string keys.
cljdoc builds & hosts documentation for Clojure/Script libraries
| Ctrl+k | Jump to recent docs |
| ← | Move to previous article |
| → | Move to next article |
| Ctrl+/ | Jump to the search field |