I use visual studio code, it allows me to put breakpoints in the code launch to debug with chrome and step and inspect the code in one editor. The first time ( a few months ago) that I started to use Budo everything worked well. But at some point, I updated to the new version and the breakpoints are not hit anymore, but I kind of found a workaround.
if my npm script is:
"start": "budo index.js:index.js --live -- -t brfs"
it works but something is wrong ( i'll explain below)
but this doesn't work
"start": "budo index.js:bundle.js --live -- -t brfs"
So the one that works as something odd. When the breakpoints hit it actually hit in the file input.js which is exactly the content of my index.js file.
I realize that it is most likely not a Budo issue, but maybe you know where I can look for.
Hi Matt,
I use visual studio code, it allows me to put breakpoints in the code launch to debug with chrome and step and inspect the code in one editor. The first time ( a few months ago) that I started to use Budo everything worked well. But at some point, I updated to the new version and the breakpoints are not hit anymore, but I kind of found a workaround.
if my npm script is: "start": "budo index.js:index.js --live -- -t brfs" it works but something is wrong ( i'll explain below)
but this doesn't work "start": "budo index.js:bundle.js --live -- -t brfs"
So the one that works as something odd. When the breakpoints hit it actually hit in the file input.js which is exactly the content of my index.js file.
I realize that it is most likely not a Budo issue, but maybe you know where I can look for.
thanks again for all your good work!