-
-
Notifications
You must be signed in to change notification settings - Fork 774
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sourcemaps #2249
Comments
I am interested in this issue. But it is a year old. Is any planing or research on this subject done? |
Not that anyone has shared with me. |
Hello there, i've started work on this over at my fork on branch It's not in a place where I want to submit it for review, but so far I've managed to produce a basic sourcemap for a test Gleam module. This is it, visualized. I was able to make debugging work through {
type = "pwa-node",
request = "launch",
name = "Debug gleam program",
-- NOTE: This wont work if the project's name doesnt match the folder name
-- This should ideally be the name variable in the Gleam.toml manifest
program = "${workspaceFolder}/build/dev/javascript/${workspaceFolderBasename}/gleam.main.mjs",
cwd = "${workspaceFolder}",
outFiles = {"${workspaceFolder}/**/*.mjs"},
resolveSourceMapLocations = {"${workspaceFolder}/build/dev/javascript/**/*.map"},
sourceMaps = true,
pauseForSourceMap = true,
} Is anyone actively interested in this, and willing to provide feedback ? |
I think people are interested for sure! |
So that exceptions and debugging tools can show Gleam syntax and line numbers.
The text was updated successfully, but these errors were encountered: