2

EDIT: Source Map works in Firefox, but not in Chrome or Edge.

When I'm debugging warnings/errors, I click on the TSX file and it pulls up an obfuscated version of the .ts/tsx file. The following screenshots will help clarify my issue...

When I get a React error like this enter image description here

I click on the /components/AddObject/index.tsx link and it opens the file in the console, but it looks like this

enter image description here

Here's what my webpack config looks like (using devTool: 'eval-source-map')

enter image description here

Any thoughts as to why my source-map file is behaving this way?

dmathisen
  • 2,269
  • 3
  • 36
  • 63
  • 1
    Does this answer your question? [Debugging typescript with source maps and webpack](https://stackoverflow.com/questions/42881493/debugging-typescript-with-source-maps-and-webpack) – Avinash Thakur Jul 15 '21 at 17:14
  • Eh. Unfortunately, no, still no luck :( – dmathisen Jul 15 '21 at 19:31
  • you can also enable source-map in tsconfig.json. This works for me in my backend. More info here: https://code.visualstudio.com/docs/typescript/typescript-compiling – Avinash Thakur Jul 15 '21 at 21:17
  • Hmm. No, still no luck. I just added an edit - source map works in Firefox, but not in Chrome or Edge. I guess I need to go back to the drawing board. – dmathisen Jul 16 '21 at 00:10
  • did you try with simply eval ? – xdemocle May 05 '22 at 18:27

0 Answers0