Running explorer locally?

[rohitpaulk]

The explorer feature on the playground is super useful. Is there a way to run the explorer locally?

This is the output I see when running fizz locally (I'm on 0.2.0):

Model checking test.json
configFileName: fizz.yaml
fizz.yaml not found. Using default options
StateSpaceOptions: options:{max_actions:100  max_concurrent_actions:2}  deadlock_detection:false
Nodes: 1, queued: 0, elapsed: 937.292µs
Time taken for model checking: 945µs
Writen graph dotfile: out/run_2025-09-23_22-40-28/graph.dot
To generate svg, run: 
dot -Tsvg out/run_2025-09-23_22-40-28/graph.dot -o graph.svg && open graph.svg
Valid Nodes: 1 Unique states: 1
IsLive: true
Time taken to check liveness: 238.75µs
PASSED: Model checker completed successfully
Writen 1 node files and 1 link files to dir out/run_2025-09-23_22-40-28

The command to generate an SVG generates the states graph, but I don't see anything related to getting an explorer-like view.

[jp-fizzbee]

Hi Rohit, you can run the explorer locally, but at present it is only available when built from source.

It was fixed in #158, but I haven't updated the documentation.

cd explorer
npm install

And,

npm start -- /path/to/the/directory/containing/stategraph/pbfiles/

For your case, it would point to out/run_2025-09-23_22-40-28 (but with appropriate path prefix - either relative or absolute.)

---

I will add it to the binary release soon. (I am just figuring out how to make an npm service as an installable binary) If you have any experience with it, it would be awesome.

The release binaries are built with this script.
https://github.com/fizzbee-io/fizzbee/blob/main/release/build_release.sh