sverweij
commented
1 year ago Hi @zachallaun thank you for your interest in state-machine-cat - your use case looks like a nice one :-)
state-machine-cat is written as ES modules - and these modules (in src) are part of the distribution on npm. They're not in dist, but in src
The package.json contains the information for any environment to either pick ESM or commonjs via the module attribute and the exports.
In short - I'd expect ESM use of state-machine-cat to already work out of the box.
zachallaun
First off, thanks for the great project!
I'm trying to use state-machine-cat as a visualization tool for an Elixir statechart library I'm working on. The visualization is embedded in a live notebook that is ultimately powered by another library called Kino.
By far the easiest way to manage external dependencies with Kino is by embedding through a CDN, but the engine only understands ESM. I'm making this work for now by essentially bundling an ESM build using esbuild and arguments very similar to these, but if you would consider including an esm build in your
distfolder, I'd be able to easily use a tool like jsdelivr.com, which would be just dandy.Proposed Behavior
Include an esm build in
dist.Current Behavior
Includes only a commonjs build.
Considered alternatives
I can get around this by generating an esm bundle myself, but this means checking a large bundle into my project to distribute it and setting up JS asset tooling.