This is great, thanks, @jorenbroekema! Since Style Dictionary itself converts token names into their appropriate platform-specific format, do you see a future opportunity to expose those as part of style-dictionary/utils?

You can kind of access those already by doing StyleDictionary.hooks.transforms['name/kebab'].transform(token) => outputs the transformed token name.

So in a sense they're already exposed, all of the built-in hooks of StyleDictionary are, on the hooks prop on the module. I think this is fine but perhaps needs better documentation.

The utils entrypoint could potentially also make for a good place to expose them though, I do agree with that, or maybe we'd have a style-dictionary/transforms and /formats entrypoints for exposing just the transform and format functions (without their filters, name, and other sibling props like that?). I'm just not really sure how big the benefits of that are and if it's worth it to maintain extra entrypoints for our built-ins.
I low-key feel like this would be great for a plugin/integration package with Style Dictionary like sd-transforms or style-dictionary-utils to maintain these kinds of things. I would love it for example if someone came out with an iOS / Android integration package for Style Dictionary with a ton of transforms/formats for those mobile platforms, as the built-ins in Style Dictionary are admittedly not the best.

For what it's worth, I ended up creating a custom action instead of a format because of complications stemming from #1063. Not perfect, but it worked fairly well.