source map hell #17321
Unanswered
daniellacosse
asked this question in
Help
source map hell
#17321
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
been hitting my head against this issue for a while. with the inline eval source maps, our dev server currently generates multiple 20MB bundles. this greatly bogs down our dev env with all the eval calls and JIT overhead.
the production build is... wildly different, with all the chunks summing to 3MB. there are perf issues there too, but milder, and It's become very difficult to isolate which is causing what performance loss - you know, use development to find out what's causing the performance issues on production without the source maps getting in the way.
for the life of me i cannot get them to split out into their own
.map
files or remove them on development entirely. (the former would be nice for sentry support)I have tried:
@zeit/[email protected]
and configuring it several different waysexperimental.productionBrowserSourceMaps
I'm desperate. please help.
next.config.js
.bablerc
- yes removingsourceMap: true
here doesn't seem to work eitherpackage.json
Beta Was this translation helpful? Give feedback.
All reactions