bytecodealliance / bytecodealliance/ComponentizeJS

Debugger Integration

未关闭
#49 0 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Rust
星标
391
派生
53
平均合并
3 天 5 小时
30 天内合并 PR
1

描述

Brought up at CTW - Spidermonkey has a debugger API that we should figure out the right integration for.

Unfortunately it does not include a debugging protocol itself, so one would need to be implemented on top of WASI sockets or otherwise. Apparently VSCode solved this for Python using a character device on preview1 to handle the V8 debugging protocol.

The debugging that needs to be handled is stepping through the JS code, when yielding through to external component model import calls, I suppose this would suspend the entire debugging interface while the external call is made, then reinitiate the debugging interface after that. This seems fine as far as I can tell.

We could possibly even have a first-class world import for debugging support, by exposing the world for debug builds only, and then relying on hosts that support the debugger protocol imports and exports, as an alternative to implementing it on top of wasi sockets.

Should be a really interesting project!

贡献指南

这个仓库没有索引到贡献指南

调研方向

未指定文件、测试或入口点。首先比较 SpiderMonkey 的调试器 API 与 VSCode Python/V8 方案,以及提议的 WASI-socket 或 first-class world-import 选项;当选定一种支持单步执行 JavaScript 并处理外部 component model import 调用的集成方案时,即视为完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
javascript, rust, vscode, wasm
领域
developer-experience, devtools
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
需要澄清
新手友好度
20/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。