Re:Show HN: We made an MCP server so Cursor can debug Node.j...
by wordofx on Saturday March 22, 2025 @04:25PM
(#43448374)
I used to run into dead loops until I changed the way I prompt cursor. Asking it to focus on 1 error at a time massively improves the success rate. Had an old project in node 10 project that hadn’t been touched since ~2017 and after several attempts with cursor. Asked if to fix 1 issue at a time until it moved from node 10>12>14…>22 and after about 15 minutes it succeeded. That included updating all the dependencies and removing deprecated/dead/dropped packages and getting them to latest and updating Vue from 1 to 3.5
[ Parent
| on HN ]
Re:Show HN: We made an MCP server so Cursor can debug Node.j...
by 30minAdayHN on Saturday March 22, 2025 @11:59PM
(#43450810)
That's a great tip. Similarly, when implementing features, breaking down into simpler things and making it focus on each step works really well.
We (co-author here) even tried to build a design doc tool that can fed to Cursor in that effect.[1]
[1] https://updates.priyank.ch/projects/2024/03/01/introducing-a...
Re:Show HN: We made an MCP server so Cursor can debug Node.j...
by arthurgousset on Tuesday March 25, 2025 @04:39PM
(#43475697)
Thanks for sharing!
> Asking it to focus on 1 error at a time massively improves the success rate.
Out of curiosity, how do you tell Cursor about the bug? Do you copy/paste console messages from the terminal into the prompt?
Re:Show HN: We made an MCP server so Cursor can debug Node.j...
by wordofx on Friday March 28, 2025 @03:26PM
(#43509088)
In cursor you can whitelist commands. So I white list npm run. Then tell cursor to upgrade a dependency and run npm run build and if there’s errors. Fix the first error and repeat. Once the build is successful, run npm test and fix 1 test at a time.
Takes some learning but once you figure it out it’s insanely powerful.