原文
| ||||||||||||||
| ||||||||||||||
![]() |
原始链接: https://news.ycombinator.com/item?id=43446659
代码编辑器Cursor有时会陷入调试循环中。为此,Hyperdrive Engineering的开发者创建了一个原型MCP(机器控制协议)服务器,允许Cursor直接在运行时调试Node.js应用程序。这避免了Cursor仅仅依靠插入`console.log`语句的需要,虽然有时这很有帮助,但并不总是高效的。该项目已在GitHub上开源 (github.com/hyperdrive-eng/mcp-nodejs-debugger),旨在为Cursor提供对应用程序行为更深入的洞察,帮助其摆脱这些低效的循环。开发者正在寻求对该原型的反馈,希望对改进Cursor的调试能力感兴趣的用户能够参与。他们试图解决的问题是Cursor容易陷入重复性、低效的调试循环,这是一个在在线论坛中经常被强调的常见问题。
| ||||||||||||||
| ||||||||||||||
![]() |
We thought: "What if Cursor could access Node.js at runtime?". That would save it from adding `console.log` everywhere, and still get out of dead loops.
We looked into it and got Cursor to debug Node.js on its own.
It's a prototype, but if you're interested in trying it out, we'd love some feedback!
Github: github.com/hyperdrive-eng/mcp-nodejs-debugger
---
References:
[1]: "At this point I feel like giving up on Cursor and just accept that WE'RE NOT THERE YET." ~Source: https://forum.cursor.com/t/cursor-for-complex-projects/38911
[2]: "We've all had the issue. You're trying to build a complex project with your AI companion. It runs into a dead loop, coding in circles, making suggestions it already tried that didn't work." ~Source: https://www.reddit.com/r/ChatGPTCoding/comments/1gz8fxb/solu...
reply