@martinklepsch: make sure you have the remote debugging enabled. If so, it requires some fiddling sometimes, as in: close the panel, reload, reopen.
I do have the remote debugging enabled (I think otherwise the panel wouldn't open)
Tried restarting a few times but didn't help, will look more into it later
@martinklepsch: Iβm back. The Dirac Runtime installed in your page is too old. Current version is 0.6.0, yours is 0.2.0.
this might explain more about upgrading: https://github.com/binaryage/dirac/blob/master/docs/upgrading.md
@darwin: thanks, that helps. I noticed the difference but somehow assumed that there might be different versions for runtime/server/extension
That solves it π
no problem, newer versions should give you better error feedback, it just happened that the 0.2.0 is so old that it donβt even have dirac.runtime/installed?
function
enjoy! bug reports / feedback welcome π
is there a way to tell chrome to always set the remote debugging port as expected by dirac?
no, AFAIK, you have to do it from command-line
but a simple wrapper script solves it for me, or a bash alias
it is also good practice to use a separate chrome profile when developing, so such script is handy anyways
not only for that chrome debugger port setting
> WARNING: The version of connected DevTools is old. Expected '0.6.0', got β0.4.0β¦ @darwin: nice! the improved documentation and sanity checks in the latest version work great π