Debugging the Gleam code rather than the compilation output

[sz3lbi]

When questions about debugging Gleam code were posted in the Gleam Discord, the response was that we should use the debugger provided by our project's runtime (debugging generated Erlang or JavaScript code). This makes sense, but I see that the Elixir LSP provides an implementation for the Debug Adapter Protocol. If I understand correctly, it allows us to debug Elixir code when running the Erlang code it was compiled to under the hood.
This made me curious. Is it not possible to implement something similar in Gleam because of the language's multi-target approach? Would it require too much effort? Are there other reasons behind it?
Coming from object-oriented languages, I am used to debugging with IDEs' built-in tools. I'm getting used to debugging like it's done with functional programming, so with echo. However, I would like to know why the above isn't feasible for Gleam. It would be nice to see the Gleam code in the debugger instead of the output that it was compiled to.

[giacomocavalieri]

I'm not familiar with the protocol but I'm sure we could somehow implement DAP for Gleam as well seeing how it's implemented for Elixir and many other languages.
The main issue is it could be a huge undertaking and require significant maintenance effort as well, and I'm not sure it's something we have the capacity for at the moment given there's many other places where we could be improving the language and ecosystem as well!

[GearsDatapacks]

JavaScript supports sourcemaps, which means if we implement those on the JavaScript target, JavaScript debuggers will be able to step through the generated code as if it's Gleam code. Some work was done on that, but the PR's author did not complete it.
On Erlang I'm not really sure, but from what I heard before it's a much more complicated system which would be a bigger undertaking.

[lpil]

Elixir has a canonical runtime so they can wrap its debugger. Gleam does not.

A community project could implement the protocol and expose the BEAM debugger for Gleam, there's nothing that would be needed from the core team to do this.

Note that's how it is in Elixir, it is a community project and not provided by core.