Which version of @angular/core won? Who provided it? Why did that remote end up with its own copy?

The negotiation happens once at startup — then it disappears into the import map. Native Federation DevTools reads it back out of the running page and explains it: every shared package, every remote, every chunk. Evidence, not guesses.

What you get

• 📦 Packages — the negotiation, per package: every candidate version, who declared which range, which file actually serves it. Conflicts are called out, not averaged away.
• 🛰️ Remotes — each participant from its own point of view: what it exposes, what it declares, and where every single dependency really resolves.
• 🕸️ Graph — remotes, dependency copies, and chunks as one traceable picture. Hover to trace, click to filter.
• 🗺️ Import Map — the effective map, row by row, each entry attributed to its package, its provider, and the chunk bundle that serves it.
• 📤 Export JSON — freeze the entire snapshot to a file. Doubles as a reproducible bug report.
• 🔒 Read-only, zero permissions — no host permissions, no content scripts. The panel inspects; it never mutates the page. Enforced by tests, not by convention.

In progress: Diagnostics (registry↔map lint) and global search.

Hover to trace

One hover answers "who shares this — and which files does it load?"

Dashed nodes are isolated copies, dotted edges are borrowed dependencies — the sharing story is visible at a glance.

Every negotiation, explained

Four participants declared @angular/core — one version won, three were not selected, and every mapped file is accounted for, SRI included.

Every remote, from its own point of view

Exposes, provided packages, and — line by line — which dependency this remote consumes from whom, and which own version lost the negotiation.

Requirements

Requires the v4 Orchestrator. The panel reads the registry that @softarc/native-federation-orchestrator keeps in the page (window.__NATIVE_FEDERATION__). Applications on the classic v3 runtime (@softarc/native-federation-runtime) do not expose this registry and are not supported — on such pages the panel shows No Native Federation detected.

Install

🛒 Chrome Web Store: coming soon — the extension will be published under the official Native Federation presence. Until then, install it from a GitHub release. No build toolchain needed — it takes about a minute.

From a release

1. Download native-federation-devtools-<version>.zip from the releases page and unzip it into a folder of its own (the zip has no top-level folder). Keep that folder — Chrome loads the extension from it.
2. Open chrome://extensions in Chrome — type it into the address bar.
3. Turn on Developer mode (toggle in the top-right corner).
4. Click Load unpacked and select the unzipped folder.
5. Open Chrome DevTools (F12, or Ctrl+Shift+I / ⌥⌘I) on an application that runs the v4 Orchestrator. The panel appears as a new Native Federation tab — if DevTools was already open, close and reopen it once.

Unpacked extensions do not update themselves. To upgrade, unzip the new release into the same folder and click the ↻ reload icon on the extension's card in chrome://extensions. Automatic updates come with the Web Store.

From source

Contributors can build the extension themselves — see Development & Architecture.

Native Federation ecosystem

Documentation

• Development & Architecture — build, run, test, repository layout, and the design constraints behind the tool
• Resolution data model — how a captured snapshot becomes the model behind the views

About

Developed and maintained by Lutz Leonhardt as part of the official Native Federation project.

Built in an agentic workflow with Claude Code and Codex as pair programmers — architecture, review, and verification stay with the maintainer.

Licensed under MIT.