Enable sourcemaps in dev #457
Conversation
| @@ -8,7 +8,7 @@ const path = require('path') | |||
| const isDevelopment = process.env.NODE_ENV !== 'production' | |||
| module.exports = { | |||
| entry: './src/index.tsx', | |||
| devtool: 'source-map', | |||
| devtool: isDevelopment ? 'eval-source-map' : 'source-map', | |||
There was a problem hiding this comment.
🤔 I remember having no issues with debugging Unovis from the dev app. Was the error in the console also leading to the obfuscated bundle?
Also the source-map option generally produces better results that 'eval-source-map' and is more computationally expensive to calculate. Do you know why the eval-source-map works here better here?
There was a problem hiding this comment.
This change changes the error message from pointing to bundle.js to pointing to something from node_modules. That's arguably an improvement, but actually it's not that much better, since we still are not getting the line numbers for the original error. Happy not to merge this, maybe it's just a weird case I'm dealing with. Thanks for reviewing!
There was a problem hiding this comment.
But overall, the source maps don't seem to be working.
For example, when I add this change:
I get this error:
The source maps don't seem to be doing their job. Instead of bundle.js it should resolve to the specific line number and source file, but it does not.
There was a problem hiding this comment.
After changing it to eval-source-map, the line numbers DO resolve correctly.
There was a problem hiding this comment.
My setup:
- Node v22.8.0
- Mac
I wonder if this is not a problem for others?
Closes #456
Before:
After: