Generate complete source maps #6756
Conversation
The source maps generated previously were mapping the bundled files to the post-Babel files - they weren't showing mapping to the source files as written. It looks like this was a result of `reactify` being used in addition to babel - that transformation must have dropped the source maps. `reactify` still needs to be listed as a dependency because it is an unlisted requirement of the `boron` package, which we use. We don't need to use it to create our bundles though, as Babel already performs the transformations we need.
|
|
|
I should add some context about that - @kumavis already created an issue for this problem. It looks like that library isn't actively maintained though. Perhaps it's worth investigating a few of the forks discussed in this issue. But yeah, as long as we're still using Edit: Well, after reading that issue again, that fork doesn't show that much promise for us. The alternate proposed, |
|
We're using |
|
I was curious whether removing |
The source maps generated previously were mapping the bundled files to the post-Babel files - they weren't mapping to the source files as written.
It looks like this was a result of
reactifybeing used in addition to babel - that transformation must have dropped the source maps.reactifystill needs to be listed as a dependency because it is an unlisted requirement of theboronpackage, which we use. We don't need to use it to create our bundles though, as Babel already performs the transformations we need.Before changes:
After changes:
