- Lucas' Newsletter
- Posts
- Daily Dispatch 27 - Debugging Issues
Daily Dispatch 27 - Debugging Issues
![](https://media.beehiiv.com/cdn-cgi/image/fit=scale-down,format=auto,onerror=redirect,quality=80/uploads/asset/file/db6a1ebd-3cea-4150-861f-de24bdd75761/pexels-photo-239548.jpeg?t=1722263354)
So hello, it’s been a while, and I haven’t being keeping up with my daily dispatches, or maybe my days are longer than yours. Relativity man, who knows?
So I was playing around with a Node.js (nodejs.org) project hosting it using Docker alongside a Postgres database.
And I was all happy and dandy until I wanted to debug an error on VSCode.
And I couldn’t.
So I went far and wide, talked with many friends (I wish), and came across this cool article Debugging uncompiled Typescript code running on a Docker container | by Mitsuhide Ohi | Medium.
This article pointed me towards the right direction, but I had to add a few things.
1 – First of all, I didn’t need to add a debug script to my package.json. I merely replaced my --inspect flag with itself + server_address:port --inspect=0.0.0.0:9229.2 – I did add the next line on my tsconfig.json.
3 — Here’s where things differ a lot from the article, my vscode launch.json configuration didn’t use the sourceMapPathOverrides (it did nothing for me).
Instead I replaced it with these two cool properties ( remoteRoot and localRoot):
4 – Now to the docker-compose.yml file, I added to my mainApp service the docker port for debugging
5 – After all that, I had to run docker-compose up -d --build --force-recreate since I changed the docker-compose.yml file.
And then BOOM! It worked.