tools
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
$ npm i node-nightly -g
$ node-nightly --inspect index.js
http://blog.sqrtthree.com/2016/02/29/debugging-nodejs-in-chrome-devtools/
devtool
基于 Electron 将 Node.js 和 Chromium 的功能融合在了一起。它的目的在于为调试、分析和开发 Node.js 应用程序提供一个简单的界面。
体验比较好, 分析(可以使用console.profile() 等接口)能力很棒 但看起来会侵入代码, 污染 window 等变量
node-inspector
使用 remote debug 协议, 不污染环境变量
iron-node
同样基于 Electron 的调试器。包含了一个内置的命令来重新编译原生插件，还有一个复杂的图形界面显示您的package.json 和 README.md。
WebStorm 内置调试器
体验很好和 WebStorm 集成, 可以在调试时修改和编辑你的文件, 运行在一个真正的 Node/V8 环境中, 但缺少一些功能:
- 一个丰富的互动的控制台
- 异常时暂停
- 异步堆栈跟踪
- Promise 检查
- 分析
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names index.js as a sample entry point and mentions package.json and README.md in the iron-node description, but identifies no repository file or test to change. Start by determining the intended documentation scope from the linked debugging tools and define a concrete comparison or update target; done requires an agreed documentation change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- electron, javascript, node.js
- Domain
- devtools
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100