You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems that the inlined sourcemaps you generate cannot be read by Visual Studio / IE, and consequently breakpoints are not hit etc.
The error in console is: "SourceMap data:application/json;base64 ... read failed: The URI prefix is not recognized". Visual Studio 2013 Ultimate update 4 with TypeScript 1.3, IE 11.
Or am i missing something? It seems weird that tsify would not work with the official / most fully featured / most widely used TypeScript IDE...
The text was updated successfully, but these errors were encountered:
Sounds like a missing feature in IE 11. That said, the problem is not related to tsify specifically; the generated sourcemaps are consumed by Browserify to create the final inlined sourcemap that you see. If IE 11 is missing complete sourcemap support, you can work around it pretty easily by using e.g. thlorenz/exorcist as a part of your build workflow.
If you have any problems with the sourcemap contents however, please open an issue here!
Yes, the root cause is definitely IE 11. What a surprise. I checked browserify's issues and they actually had request and lengthy discussion about adding support for non-inlined sourcemaps, but it was declined.
Thanks for your help and pointing to exorcist, gulp with watchify+browserify+tsify+exorcist seems to be working well with Visual Studio and IE 11.
It seems that the inlined sourcemaps you generate cannot be read by Visual Studio / IE, and consequently breakpoints are not hit etc.
The error in console is: "SourceMap data:application/json;base64 ... read failed: The URI prefix is not recognized". Visual Studio 2013 Ultimate update 4 with TypeScript 1.3, IE 11.
Or am i missing something? It seems weird that tsify would not work with the official / most fully featured / most widely used TypeScript IDE...
The text was updated successfully, but these errors were encountered: