Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Can't debug current typescript file in VS Code because corresponding JavaScript cannot be found

I am using Visual Studio Code version 1.17, and my objective is to debug the current typescript file. I have a build task running, so I always have a corresponding javascript file like this:

src/folder1/folder2/main.ts src/folder1/folder2/main.js 

I have tried with the following launch.json configuration:

{   "type": "node",   "request": "launch",   "name": "Current File",   "program": "${file}",   "console": "integratedTerminal",   "outFiles": [     "${workspaceFolder}/${fileDirname}**/*.js"   ] } 

But I get the error: Cannot launch program '--full-path-to-project--/src/folder1/folder2/main.ts' because corresponding JavaScript cannot be found.

But the corresponding JavaScript file exists!

tsconfig.json:

{ "compileOnSave": true, "compilerOptions": {     "target": "es6",     "lib": [         "es2017",         "dom"     ],     "module": "commonjs",     "watch": true,     "moduleResolution": "node",     "sourceMap": true     // "types": [] }, "include": [     "src",     "test" ], "exclude": [     "node_modules",     "typings" ]} 
like image 318
DauleDK Avatar asked Nov 05 '17 19:11

DauleDK


People also ask

How do I enable JavaScript debugging in Visual Studio code?

To run or debug a simple app in VS Code, select Run and Debug on the Debug start view or press F5 and VS Code will try to run your currently active file. However, for most debugging scenarios, creating a launch configuration file is beneficial because it allows you to configure and save debugging setup details.


2 Answers

The problem may be with your map files and not with configuration.

Before trying anything else you want to make sure your paths that you are using in your launch configuration are correct.

You can do so by substituting the paths with absolute paths on your system temporarily to see if it works.

If it does not work you should:

Check your tsconfig and make sure mapRoot under compilerOptions is not set to anything. This is what official documentation has to say about it:

Specifies the location where debugger should locate map files instead of generated locations. Use this flag if the .map files will be located at run-time in a different location than the .js files. The location specified will be embedded in the sourceMap to direct the debugger where the map files will be located.

You can read more about it here

In most of the cases, you don't really want to set it to anything.

Also, make sure that

"sourceMap": true`

is set in compilerOptions in tsconfig.json and map files are getting generated.

like image 98
Aakash Malhotra Avatar answered Sep 24 '22 07:09

Aakash Malhotra


The configuration for your outFiles points to the wrong directory.

Replacing your launch.json config with this would fix it:

{   "type": "node",   "request": "launch",   "name": "Current File",   "program": "${file}",   "console": "integratedTerminal",   "outFiles": ["${fileDirname}/*.js"] } 

From the vscode launch.json variable reference:

${fileDirName} the current opened file's dirname

should be the directory you need.

Note that you can also use "outFiles": ["${fileDirname}/**/*.js"] to include subdirectories.

The configuration you're using adds the following directory:

"${workspaceFolder}/${fileDirname}**/*.js" 

Which translates to something like:

"/path/to/root/path/to/root/src/folder1/folder2/**/*.js" 

i.e. the path to the root is in there twice, making it an invalid path.

If your .js files are on a different outDir: simply use the path to such directory. Typescript sourceMaps will do the rest.

For example, if you put your .js files in a dist directory:

"outFiles": ["${workspaceFolder}/dist/**/*.js"] 
like image 34
lucascaro Avatar answered Sep 25 '22 07:09

lucascaro