What about debugging and recording stack traces too?
"DevTools Protocol API docs—its domains, methods, and events": https://github.com/ChromeDevTools/debugger-protocol-viewer .. https://chromedevtools.github.io/devtools-protocol/
ChromeDevTools/awesome-chrome-devtools > Chrome Debugger integration with Editors:
https://github.com/ChromeDevTools/awesome-chrome-devtools#ch...
DAP: Debug Adapter Protocol > Implementations: https://microsoft.github.io/debug-adapter-protocol/implement... :
- Microsoft/vscode-js-debug: https://github.com/microsoft/vscode-js-debug :
> This is a DAP-based JavaScript debugger. It debugs Node.js, Chrome, Edge, WebView2, VS Code extensions, and more. It has been the default JavaScript debugger in Visual Studio Code since 1.46, and is gradually rolling out in Visual Studio proper.
- awto/effectfuljs: https://github.com/awto/effectfuljs/tree/main/packages/vscod... :
> EffectfulJS Debugger: VSCode debugger for JavaScript/TypeScript. Besides the typical debugger's features it offers: Time-traveling,
Persistent state,
Platform independence,
Programmable API,
Hot mocking of functions or even parts of a function,
Hot code swapping,
Data breakpoints.
This works by instrumenting JavaScript/TypeScript code and injecting necessary debugging API calls into it. It is implemented using EffectfulJS.
https://github.com/awto/effectfuljs : @effectful/debugger , @effectful/es-persist: https://github.com/awto/effectfuljs/tree/main/packages/es-pe...