busterjs/buster — Issue #22: The server/browser runner is currently undebuggable
Author: cjohansen
Created: 2011-12-09 12:19:32+00:00
State: open

If you like using a step debugger, you'll face problems with the server because it namespaces paths with the session id for every run. That means the browser never sees the "file" you put the break-point in, causing step debuggers to not do anything useful at all.

Could we perhaps serve files over a /sessions/current/ URL or something like that to avoid this problem?