Stack trace refers to the VM code
gajus opened this issue · comments
Current behaviour
When a runtime error originates in a bundle, the stack trace refers to the code executed in the bundle.
ReferenceError: props is not defined
+ at TopicIndexContainer (evalmachine.<anonymous>:485:15)
at WrappedComponent (/my-project/node_modules/react-css-modules/dist/wrapStatelessFunction.js:55:38)
at /my-project/node_modules/react-dom/lib/ReactCompositeComponent.js:306:16
at measureLifeCyclePerf (/my-project/node_modules/react-dom/lib/ReactCompositeComponent.js:75:12)
at ReactCompositeComponentWrapper._constructComponentWithoutOwner (/my-project/node_modules/react-dom/lib/ReactCompositeComponent.js:305:14)
at ReactCompositeComponentWrapper._constructComponent (/my-project/node_modules/react-dom/lib/ReactCompositeComponent.js:280:21)
at ReactCompositeComponentWrapper.mountComponent (/my-project/node_modules/react-dom/lib/ReactCompositeComponent.js:188:21)
at Object.mountComponent (/my-project/node_modules/react-dom/lib/ReactReconciler.js:46:35)
at /my-project/node_modules/react-dom/lib/ReactServerRendering.js:45:36
at ReactServerRenderingTransaction.perform (/my-project/node_modules/react-dom/lib/Transaction.js:140:20)
Expected behaviour
Stack trace must use source maps to refer to the original source code.