@Saúl Cabrera, is there a debugging story for Javy? (that is, to debug the JS code, not Javy itself)
One of my colleagues is looking at debugger support for quickjs, and I was wondering if Javy could benefit from that as well
Javy doesn't currently have anything built-in for enabling step debugging through the JS code
And it wouldn't be able to as the quickjs runtime it uses doesn't support it.
But we are planning to spend some cycles working on that for another project.
The question is: If quickjs gains debugger support, would javy be interested in adding debugging capabilities? Or that's not something you have a use case for?
That is something that we would consider integrating, yes. From a capacity perspective, we'd probably won't be able to take on the full integration (at least not myself) but we would certainly welcome contributions and we'd help with reviews etc, if that's something that you're interested in. Also, we'd probably want to discuss the high-level details through an issue first.
Related: I have been working on a set of Rust crates to process QuickJS' bytecode format, in which you could recover the debug information, in case that's useful for what you're doing (https://github.com/bytecodealliance/javy/commit/c665da7e8a6a7f4690d1914d494f14b24d8e1653#diff-6a2b3302a76dd6291072852090b9a6f28552daeae1f2aef2b26fee6c68f9f0ddR147)
This should be the right link: https://github.com/bytecodealliance/javy/blob/c665da7e8a6a7f4690d1914d494f14b24d8e1653/jac/quickpars/src/sections.rs#L147
For our use case we have access to the JS source, so probably we wouldn't need parsing the bytecode.
Would it make sense to contribute that back to the rquickjs project (assuming they are interested)? or is it javy specific?
There's been some recent discussion in the quickjs-ng repo about debugger support, and one of the approaches looks interesting and not very invasive, although it would need further refinement (e.g., adding support for locals)
https://github.com/quickjs-ng/quickjs/issues/119
Would it make sense to contribute that back to the rquickjs project (assuming they are interested)? or is it javy specific?
It's not Javy specific, it's QuickJS specific actually, so it _could_ make sense assuming they are interested.
Last updated: Feb 24 2026 at 04:36 UTC