typescript debug / breakpoint does not work

Question

Since few days, debugger does not work anymore. I've tried several things without success.

typescript 0.9.1
VS2012
IE10
the source map, JS files are updated when I save the TS files

In Visual studio at the place of the breakpoint I've got: 'The breakpoint will not currently be hit. No symbols have been loaded for this document'

Any help?
How IE load the symbols? I assume it's related to the source map ...

Thank in advance

Richard

I've had to clear the browser cache. I've had to delete the map file explicitly and rebuild. I've confirmed that the //# sourceMappingURL=/path/to/file.js.map comment is the last line in the output JS file. Usually things start to work. Sometimes, I've resorted to just adding debugger; — WiredPrairie
– WiredPrairie, Commented Nov 3, 2013 at 11:54
thk, I don't have the 'sourceMapping' line at the end of my js files. Do you know how this file arrive there? Where do you put the 'debugger;' line? — rlasjunies
– rlasjunies, Commented Nov 3, 2013 at 15:14
in fact, the line //# sourceMappingURL=/path/to/file.js.mapappears when a save the file, and then disappears when I 'F5/Run' the project. I will have a look on the build conf — rlasjunies
– rlasjunies, Commented Nov 3, 2013 at 15:30

Mika Berglund · Accepted Answer · 2014-03-02 21:49:20Z

2

I had a similar problem, but with Visual Studio 2013. No breakpoints were hit, even though I was running in debug mode and with source maps generated.

I found out that after I included the compiled .js files in the project, my breakpoints in TypeScript started hitting.

answered Mar 2, 2014 at 21:49

Mika Berglund

212 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Dmitry Matveev Over a year ago

do you use the same environment as rlasjunies or chrome or firefox? just trying to figure out if the article I linked in my answere is not off its mark. cheers :)

Chad Over a year ago

Strange, I found that when I included the JS file in my project, that this broke "compile on save" and did nothing to fix the lack of being able to step through the TS code.

Dmitry Matveev · Accepted Answer · 2014-06-23 11:35:59Z

1

The following is for people who are using Chrome or Firefox for the environment...

Apparently you just simply can't get it to work with VS but not all is lost as the author of this article shows. Hope it helps some more struggles to get debugging :)

answered Jun 23, 2014 at 11:35

Dmitry Matveev

5,3761 gold badge34 silver badges43 bronze badges

Comments

Community · Accepted Answer · 2017-05-23 12:33:11Z

Here is the answer (of my question ... with the help of WiredPrairie, ... ;-) )

This line

<Import Project="$(VSToolsPath)\TypeScript\Microsoft.TypeScript.targets" Condition="'$(BuildingInsideVisualStudio)' == 'true'" />

was preceeding my lines

 <PropertyGroup Condition="'$(Configuration)' == 'Debug'">
    <TypeScriptTarget>ES5</TypeScriptTarget>
    <TypeScriptRemoveComments>true</TypeScriptRemoveComments>
    <TypeScriptSourceMap>true</TypeScriptSourceMap>
    <TypeScriptModuleKind>AMD</TypeScriptModuleKind>
  </PropertyGroup>
  <PropertyGroup Condition="'$(Configuration)' == 'Release'">
    <TypeScriptTarget>ES5</TypeScriptTarget>
    <TypeScriptRemoveComments>true</TypeScriptRemoveComments>
    <TypeScriptSourceMap>true</TypeScriptSourceMap>
    <TypeScriptModuleKind>AMD</TypeScriptModuleKind>
  </PropertyGroup>

So I put it AFTER ( what a smart guys, isn't it ;-) ) in my *.csproj

I found the problem because:

The //# sourceMappingURL=/path/to/file.js.map was generated at the end of the *.js files when saving, not when compiling.
The build output was saying The TypeScript Compiler was given an empty configurations string, which is unusual and suspicious..

The solution comes from this post: TypeScript Compiler was given an empty configurations string.

The root cause of the problem appears when I tried to deploy my project to Azure. The js files were not uploaded/compiled, so i've added this tricky line in the csproj bad luck :-(

Thank and I hope it will help others.

MiN · Accepted Answer · 2015-07-01 20:53:39Z

1

In my case the answer was that another script file was actually used by the html. Once this was fixed, breakpoints started working, of course.

answered Jul 1, 2015 at 20:53

MiN

1852 silver badges13 bronze badges

Collectives™ on Stack Overflow

typescript debug / breakpoint does not work

4 Answers 4

2 Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

4 Answers 4

2 Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related