Where is Elm debugger?

[Misha Moroshko]

Debug.watch docs say:

Watch a particular value in the debugger.

 Where would I find the Elm debugger?

[Janis Voigtländer]

When you run your program under test from elm-reactor, do: Instead of clicking the file name, click the wrench symbol to the left of it.

​

--
You received this message because you are subscribed to the Google Groups "Elm Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elm-discuss...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Misha Moroshko]

Aha! Is this documented anywhere?

How do I enter the debugger if I embed my Elm program in index.html? There is no wrench symbol to the left of index.html

[Janis Voigtländer]

https://github.com/elm-lang/elm-reactor/blob/master/README.md#time-travel-debugging

[Misha Moroshko]

Thanks for the pointer, I'll check it out!

[Yonatan Kogan]

We were having issues with this yesterday, probably as a result of https://github.com/elm-lang/elm-reactor/issues/145. Looks like someone opened a PR for it 13 hours ago that you may be able to monkey-patch in?

[Misha Moroshko]

Janis, I'm probably missing something obvious, but where shall I find the _reactor/debug.js script? Do I need to install anything?

On Tuesday, 3 November 2015 23:32:07 UTC+11, Janis Voigtländer wrote:

[Janis Voigtländer]

At $ELM_HOME/reactor/_reactor/debug.js. Where $ELM_HOME is an environment variable that the installer should have set for you (or you have set yourself if you used the npm installer and followed the relevant README).

​

[Misha Moroshko]

Janis, my $ELM_HOME variable is empty, but I found the file in /usr/local/share/elm/reactor/_reactor/debug.js

Not exactly sure how I ended up having Elm installed without $ELM_HOME being defined...

[Misha Moroshko]

Also, looks like `Elm.fullscreenDebug` doesn't have the `args` parameter like `Elm.fullscreen`, so if I use ports I cannot use the debugger right now. Am I missing something?

[Janis Voigtländer]

I think this case is simply still unsupported.

See this thread and this issue.

​

[Simon]

Likewise when you use elm-reactor with a program that has ports then you get immediate error messages

[Pete Vilter]

Unfortunately ports are not supported in the debugger; this should be addressed in 0.16.1.

Also you shouldn't have to know where `/_reactor/debug.js` resides on the file system, because if you are visiting a page served by the reactor, it will just serve the file when you request that URL; it's effectively "built in". (Actually in 0.16.1 it'll actually be concatenated into the elm-reactor executable itself!)