Replies: 2 comments
-
What does your |
Beta Was this translation helpful? Give feedback.
0 replies
-
Did you ever find an answer for this? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
TL;DR; which option should I set to disable transpiling async/await with regenerator in a production build?
I'm running a CRA-based application with default settings.
Recently we've experienced a need to debug a production build on a file that is based on async-await. The CRA's production build is configured to transpile A/A down to ES5 using
regenerator
package (I think it's done via one ofbabel
plugins). The issue is that the code on production and our original code (available through sourcemaps) are so different that debugger jumps across the file, making ordinary debugging in the browsers pretty useless.So far I've tried a couple of different settings to alter CRA's babel settings, but none of them helped,
asyncToGenerator.js
is still there :(config-overrides.js
:Beta Was this translation helpful? Give feedback.
All reactions