Broken source-maps in `@next`?
See original GitHub issueLooks like the source-map has gone bonkers in the 2.0 beta?
It thinks node
is undefined, and somehow node.type
is a VNode
, in the same expression??
And this is a trivial example like patch(root, null, <div>LALALA</div>)
, which doesn’t work anymore…
patch.js:117 Uncaught TypeError: Cannot read property 'type' of null
at l (patch.js:117)
at Object.n [as patch] (patch.js:4)
at window.setTimeout (media.tsx:61)
I mean, all the tests were passing, so what the…?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Next + SWC appear to generate incorrect sourcemaps #39878
The SWC sourcemaps are incorrect - the mapped output differs from the original source code by a few lines, causing incorrect debugging behavior....
Read more >4 Reasons Why Your Source Maps are Broken - Sentry Blog
4 Reasons Why Your Source Maps are Broken · Missing or incorrect source map directive · Missing original source files · Bad source...
Read more >Advanced Features: Source Maps | Next.js
Enables browser source map generation during the production build. ... Adding source maps can increase next build time; Increases memory usage during next...
Read more >NextJS Source Maps stopped working on Chrome 92
Source Maps are enabled by default during development. Any idea what changes was made which broke the source map ?
Read more >Source Maps - SurviveJS
When your source code has gone through transformations, debugging in the browser becomes a problem. Source maps solve this problem by providing a...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Weird. Maybe this is a Chrome bug after all, I have seen something similar happening on another project lately, but always assumed it was due to mismatched source maps…
I am going to close here since I feel there’s nothing I can do, but if you have any ideas, please do let me know.