Paste a package.json and visualize the dependency tree as an interactive force-directed graph.
A package.json becomes a network of connected dependency nodes in this visualizer. Paste the manifest, and the tool represents recognized dependency declarations as an interactive force-directed graph so you can inspect relationships spatially instead of scanning a long JSON object. The important distinction is that package.json describes requested dependencies, not necessarily the exact installed tree. A version range such as ^4.17.21 is a requirement, and the manifest alone does not establish which release an installer selected.
Paste a complete, valid package.json object. Dependency fields associate package names with requested version or source specifiers. The visualizer maps the declarations it recognizes to nodes and links, then presents them in a force-directed layout for inspection. The graph is a visual reading of the manifest; using it does not change the JSON you supplied.
A package.json normally records the direct requirements declared by one package. It does not by itself identify every transitive package and exact version chosen during installation. Consequently, read this view as a graph of the supplied manifest. Consult the relevant lockfile or installed dependency metadata when the question concerns the complete resolved tree.
No, not from package.json alone. The manifest can contain ranges and non-registry specifiers, while an installed tree includes resolved versions and transitive packages. Treat this visualizer as a view of declarations in the pasted manifest. Inspect package-lock.json, another applicable lockfile, or the installation itself when exact resolution matters.
No. The package.json text and resulting dependency visualization stay in the browser, so this tool does not upload the manifest. That matters for private package names and internal dependency specifiers. The privacy claim covers use of this page, not copies of the graph or manifest that you separately save or share.
The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.
Format, validate, and beautify JSON with syntax highlighting and error detection.
Encode text or files to Base64 and decode Base64 strings back to their original form.
Format and indent SQL queries for better readability across all major dialects.
Convert HTML markup into clean Markdown syntax with support for tables and lists.
Write Markdown and see the rendered HTML output in real time with live preview.
Visualize unified diffs and patch files with color-coded additions and deletions.