Mostafa Moradian

@nwidger Thanks! That's actually what I am trying to achieve. Also thanks for the comments, they make sense now that I am separating CLI frontend from Goja.

### Current progress 1. Added breakpoints and the ability of the debugger to stop at breakpoints. Actions are: set, clean and list. 2. Implemented a command pattern and exposed an...

The latest code in my fork of Goja includes an API that [goja_debugger](https://github.com/mostafa/goja_debugger) taps into to control execution using an stand-alone Debugger in Goja. So, any frontend (CLI, DAP, etc.)...

@nwidger Thanks for the feedback! * I unexported it as `newDebugger` for now. It was originally exported, so it can be used to tap into the debugger, but then @MStoykov...

@nwidger Thanks for the heads-up. It's now fixed.

@nwidger I've added [on-the-fly sourcemap generation](https://github.com/mostafa/goja_debugger/commit/b17943e2771c8ce41084fc81fe0cd2b6672c6961), thanks to your suggested snippet and package.

@MStoykov added dynamic variable resolution, which results in local scoped variables to be visible to `print` and `exec`. I added `backtrace` to goja_debugger and fixed panic on `ReferenceError` in `print`...

A small demo to brighten up your day on top of the POC by @MStoykov: https://asciinema.org/a/423945

@faisalraja Like every other piece of code, it isn't perfect. There are [some issues](https://github.com/mostafa/goja/issues) that need to be addressed, plus it should conform to TC39 if there are any for...

@gedw99 Please have a look at this POC: https://github.com/grafana/k6/tree/feature/PoCDebugger And this frontend: https://github.com/mostafa/goja_debugger