咨询：能提取Node.js外部函数调用调用图的工具

Absolutely! There are several solid tools that can capture external module function calls (like your semver.compare example) and generate clear call graphs for Node.js code. Here are my top recommendations:

1. dependency-cruiser #

This tool is built specifically for analyzing dependencies and generating call/module graphs, and it handles third-party module calls seamlessly.

• Setup: Install it globally via npm:

  npm install -g dependency-cruiser
  

• Usage for your example: Run this command against your script to generate an SVG call graph:

  depcruise --output-type dot your-script.js | dot -Tsvg -o callgraph.svg
  

• What you'll get: The resulting SVG will clearly show the chain: console.log() → compare_versions() → semver.compare(), along with the module import link between your script and the semver package.

2. Clinic.js Bubbleprof #

Clinic.js is a suite of Node.js performance tools, and Bubbleprof is perfect for visualizing call graphs including external function invocations.

• Setup: Install the global package:

  npm install -g clinic
  

• Usage: Run your script with Bubbleprof:

  clinic bubbleprof -- node your-script.js
  

• What you'll get: After your script runs, a browser window will open with an interactive call graph. You’ll see bubbles representing each function call, including semver.compare nested under compare_versions, making it easy to trace the execution flow.

3. js-callgraph #

A lightweight, focused tool for generating JavaScript call graphs that explicitly includes calls to third-party module functions.

• Setup: Install globally:

  npm install -g js-callgraph
  

• Usage: Run it directly on your script for a text-based call graph, or use flags for visualization:

  js-callgraph your-script.js
  

• What you'll get: The text output will list the call hierarchy, showing that compare_versions invokes semver.compare. You can also export the graph to DOT format for converting to images if needed.

4. Node.js Inspector + Chrome DevTools #

If you don’t want to install extra tools, the built-in Node.js Inspector paired with Chrome DevTools can help you trace these calls.

• Usage:
  1. Run your script with inspect mode:

     node --inspect-brk your-script.js
     

  2. Open Chrome and navigate to chrome://inspect, then click "Inspect" next to your script.
  3. Go to the Performance tab, click "Record", then let your script run.
• What you'll get: The performance profile will show the full call stack, including the semver.compare invocation under compare_versions. You can hover over the timeline to see the exact call flow.

All these tools will capture the external function call you’re looking for in your example code. Pick the one that fits your workflow best!

内容的提问来源于stack exchange，提问作者Victor Liu