- choose a plugin to examine (e.g. atom-chlorine) and watch compile it
- start atom
- activate the plugin somehow -- this makes sure the cljs files are visible in devtools
- open devtools (ctrl-shift-i or equivalent) and choose the sources tab
- expand top -> file:// -> /home/<fill-in> -> <something>/atom-chlorine -> lib/js/cljs-runtime
- among the displayed folders and files should be some .cljs ones
- double-click a .cljs file and view its contents
- click on a number in the column to the left of the source code to enable a breakpoint -- some lines aren't such good choices (e.g. "case", "let", don't seem to yield good results)
- figure out a way to trigger the breakpoint -- by opening another project window that would trigger the plugin and loading the plugin, it might be possible to trigger a breakpoint that would only be reached early on. this might work because breakpoints appear to be saved -- even across editor restarts.
- trigger the breakpoint and use the debugger :)
- the debugger doesn't appear to be active unless devtools is open -- so even if breakpoints are set, they may not trigger
- activating (initial loading of) the plugin while devtools is open may hamper proper operation of the plugin -- so opening devtools after the plugin has activated may lead to better results