-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
[BUG] Debugging experience is very poor #44
Comments
I see two ways to fix this:
|
this is surely an issue for Rollup - it ought to be simple for them to add a sourcemap to the browser output file (I'm not sure how much the browser file is actually used). Deno supports V8 Inspector (I often use the |
It may be a Rollup issue, yes. Good point. |
FYI I have raised an issue for the particular error you reference above rollup/rollup#3934 and a PR to fix rollup/rollup#3935 in the Rollup project. Doesn’t help with the debugging aspect of this issue, but may provide some more context what the error is, why it occurs and hopefully a path forward towards fixing it. |
Describe the bug
When Rollup encounters a runtime error, it leaves you with very little to go on -- aside from a stack trace, containing mangled function names and hard-to-reach line numbers.
This doesn't really help:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
You get an un-minifed error.
The Rollup module you're importing does not come with a source map, btw.
The text was updated successfully, but these errors were encountered: