use it

# Clone this repo
git clone https://github.com/dvingo/fulcro-inspect
bb release

navigate in a web browser to:

chrome://extensions

• developer mode [x]
• Load unpacked
• pick the directory shells/chrome in this repository on your file system
• setup preloads in your app (see upstream inspector docs). refresh your app
• enjoy

---

This is a Fulcro 3 port of the fulcro inspector.

The initial-intial goal was to add UI theming support but then turned into updating the inspector to be implemented in fulcro 3.

(there is currently a dark theme and a light theme)

Status

Not fully polished, but the features are ported. There is currently ongoing work to add support for rendering the views in pathom-viz for pathom3-backed remotes.

The instructions here still apply for setting up your fulcro app:

https://github.com/fulcrologic/fulcro-inspect

Contributing

To hack on the inspector locally - with a REPL :) - see the CONTRIBUTING.md file in this repo.

some ideas of things to add:

• replicate all the views in pathom-viz for pathom3 into the inspector.
• performance profiling your views and queries (i'm thinking via adding some dev-time config when you create your fulcro app which would communicate this info to the inspector extension.)
• add more themes
• use the component registry of a fulcro app to make a tab showing all components in an app, and their fulcro-options maps

Local fulcro

It is recommended to use a local clone of fulcro as well during development in whichever fulcro app you're using to develop against.

The extension integration for fulcro apps lives in the fulcro repo and codebase:

https://github.com/fulcrologic/fulcro/tree/develop/src/main/com/fulcrologic/fulcro/inspect

so when you are developing against the inspector it can be useful to change the code in these namespaces as well, to add inline def's for example and do the usual REPL dev things to make iteration and understanding happen rapidly.