-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
Why next.js source maps are in ES5 #953
Comments
not sure exactly what prop deals with that but you could do a console.log of the actual config and change whatever you need.
Then run rnv with That way you'll see all the configs and override what you want. |
I see that you've added the |
Yes I went exactly according Sentry's documentation. There are several approaches to set up Sentry. It always shows bad code, that is in Dev tools Sources of browser. It looks like source code is twice transpilled. |
I'm new to ReNative, so I probably won't be able to help much with things potentially happening there, but I have recently evaluated the transpilation choices implicitly being made by Next.js. Some things to potentially evaluate:
|
Also, have a look at the source for some of the implicit choices for RNV while possibly changing branches/tags to your specific version of Renative:
|
|
I too found that this didn't change much. Worth noting that I was making changes and evaluating the size of the resulting bundle to determine if less things were being transpiled. None of that research was related to source maps specifically.
I found that this was essentially the default
This is where I was able to alter the implicit transpilation choices a bit more and reduce the amount of things being transpiled. One of the larger shifts was
More was just noting that although the linked source exports
Right right, might want to have a look at the linked source to understand what choices it is making including any other choices from things upstream from there too. |
Did you reproduced this issue in your side? |
Nopers, I have not. Will let you know if/when I go down the path of reproduction. I can confirm there are no source maps available by default with the starter project. |
I created new renative project based on And issue is also there:
|
Could it be considered as a bug? |
this is no longer the issue in 1.0.0-rc.18. |
I would like to have correct crash reports from Sentry lib to show exact place of error in original code.
But looks like source maps for web are not showing original code but ES5.
Is it possible to reconfigure maybe settings in next.config.js in order source maps were showing original code?
next.config.js:
The text was updated successfully, but these errors were encountered: