Release optimization pass doesn't respect input source maps? #10
Hey peeps! Nice work splitting this off from react-native :)
It seems that, despite best intentions, input source maps get ignored when bundling for release. Here is the culprit: https://github.com/facebook/metro-bundler/blob/e87a8205d8ca070df0fcef67dbe4f02389770b95/packages/metro-bundler/src/JSTransformer/worker/index.js#L126
The transform steps done inside both of those optimization passes seem to ignore input source maps, regardless of whether they are passed inline or not. This may well be an issue with Babel rather than Metro. Indeed, it may even be desired behaviour in babel, but metro should probably be mapping between compiled and input code properly :)
The first place that the input source map gets left behind is during the
However, even if you patch
I've done a few hours trying to debug this but gotten nowhere. Maybe one of you can look at it?
The text was updated successfully, but these errors were encountered: