stevedylan.dev stevedylan.dev While considering solutions for #46, I ran across https://npmx.dev/package/js-yaml that suggests using https://npmx.dev/package/yaml instead because it's smaller and has no dependencies.
And since we now use remark and friends, it uses toml and yaml packages so it's probably worth replacing both.
Actually, now that PR #46 added remark and friends, which use toml and yaml packages, it may actually be worth replacing js-yaml and smol-toml to reduce dependencies. Of course, bundled there's a lot of tree shaking that occurs, but still duplication otherwise.
Right now, it's 4.0MB post-build. I'll replace those two packages and see if it changes much. At least when I tested replacing js-yaml with yaml before, the code changes were minimal.
If I add --minify to the build script, with or without smol-toml the bundle is 2.26MB. And given toml doesn't have a stringify, seems we probably need to use smol-toml anyway.
Again with --minify and keeping both toml and smol-toml from my step above, adding js-yaml back in - with yaml still as a transitive dependency - the size goes down to 2.19MB!
I think the take-away is to add --minify but otherwise keep things as-is.
I tried this. With
js-yamlthe entry point is 3.67MB. Withyamlit's 3.82MB. That said, the community saysjs-yamlappears unmaintained: https://e18e.dev/docs/replacements/js-yaml#replacements-for-js-yamlThat doesn't seem to be the case, though. According to npmx,
js-yamlwas last published 2026-05-31.yamlwas last published 2026-05-11.But the community also said
js-yamlhas spec issues. Seems good enough for our case. I'm going to go ahead and publish the branch - even make a PR - but will close this issue. @stevedylan.dev, if you want to take it or not, it's all good. Figured it's at least worth having as a PR for posterity if nothing else. There were a couple small changes to call sites, but tests were unchanged.