disable typescript sourcemaps

Hi

There is something not quite right about the typescript sourcemap integration and setting breakpoints.

I find that if I open a .ts file and set a breakpoint then the breakpoint is shown in chrome debugger but it is not triggered; I cannot set a breakpoint in the generated js (I guess enabling source maps prevents this).

If I delete the sourcemap directive from the generated sourcemap file, then I can set a breakpoint in the js and this actually causes breakpoints to work in the .ts.

I cannot reproduce a simple scenario and I read this thread (http://devnet.jetbrains.com/message/5477457#5477457) - is this still applicable?

I am happy working without sourcemaps as typescript generates such nice javascript but if I go into the Filewatcher and remove the create source maps directive, it still generates the sourcemap.

Is disabling source map generation possible within webstorm?

James

1 comment

Hi James,

yes, http://youtrack.jetbrains.com/issue/WEB-6413 is still actual.

>I am happy working without sourcemaps as typescript generates such nice  javascript but if I go into the Filewatcher and remove the create source  maps directive, it still generates the sourcemap.

You must have done something wrong. Sourcemaps are generated by the trainspiler, so removing the corresponding option from file watcher arguments should disable source map generation. How many file watchers do you have? Can you attach a screenshot of your typescript file watcher settings?

0

Please sign in to leave a comment.