ToolJovia
Developer

Static Module Dependency Graph

Map supplied JavaScript modules, unresolved imports and dependency cycles locally.

✓ Browser-local processing

Loading tool…

How to use Static Module Dependency Graph

Map supplied JavaScript modules, unresolved imports and dependency cycles locally. Provide a JSON filename-to-source map. The tool parses static import/export declarations, resolves exact relative virtual filenames, and reports cycles. Bare package names and unsupplied files remain unresolved; nothing is fetched.

  1. Provide json object: relative filename → module source.
  2. Choose the supported mode and run the tool. Review its assumptions and any reported errors.
  3. Copy the result or download a separate output; reset to clear the current form.

Good to know

  • 1–50 modules,200,000 aggregate input characters,50,000 per source and2,000 static edges. Explicit ECMAScript2022 only.
  • Exact virtual paths only; no extension guessing, package resolution, dynamic-import resolution, filesystem reads or import fetching. Escaping the supplied virtual root is rejected.
  • 10-second library startup and2-second isolated computation limit.
  • Inputs are processed on this device and are not automatically saved or uploaded.

Common questions

Why is an import marked unresolved?

Only exact relative filenames in your JSON map can resolve. Package names, URLs, omitted files and implicit extensions are deliberately left unresolved rather than guessed.

Does this change my original input?

No. The tool returns a separate result. Review that output before using it in another application.

Keep going with related tools

All developer →