Visual Studio Code and spotting bugs in API Now that everything is set up, it’s time to check where the bug is hiding in the API. It is very helpful to create tasks consisting of several interdependent subtasks. You can set the type of the task, whether it will be an npm script or a shell. One of the properties of the tsconfig.json file comes to our aid: Īs you can see, the file with tasks is not complicated. The converted code loses its readability and it would be difficult to check it for errors, so I bet you prefer to check the TypeScript code. Here the situation changes because the code is written in TypeScript which is converted to JavaScript. The API from the first part of the series was written in JavaScript, so when you launched the debugger, you went through the code we wrote. The API aims to provide a simple CRUD to handle books and save them in the database. Wondering what the reflect-metadata library does in this file? You’ll need it for the correct operation of decorators used in models with TypeORM. All used libraries can be found in the package.json file. The project is a simple API written in TypeScript using the Express.js framework with the Postgres database using TypeORM.

Visual studio code debug node