package.json Exports Resolver
Paste package.json exports plus a specifier to trace Node conditional exports, import/require/types branches, blocked subpaths and invalid export targets.
When to use ExportMap Resolver
Use this when Node, TypeScript or a bundler reports ERR_PACKAGE_PATH_NOT_EXPORTED or resolves a different branch than you expected. The trace explains which export key and condition was selected.
package.json Exports Resolver - ERR_PACKAGE_PATH_NOT_EXPORTED Checker
The package exports field is powerful because it defines the public surface of a package, but that also means internal file imports can be intentionally blocked. Many resolution bugs are caused by a missing subpath export, a missing default condition, a types branch mismatch or an invalid target.
ExportMap Resolver is deliberately narrower than a full npm package analyzer. It accepts the package.json you already have and one import specifier, then produces a branch-by-branch trace that is easy to paste into an issue, pull request or release checklist.
The tool does not install packages or inspect built files. It checks the map logic and common structural hazards so you know whether the next step is to change package.json, update the import path or run a deeper package publishing audit.
- Runs in the browser for fast first-pass analysis.
- Does not require login, upload, server storage or build access.
- Works best with redacted snippets copied from DevTools, config files, framework examples or issue reports.
- Findings are practical review signals and should be confirmed with the official toolchain before production changes.
The package exports field is powerful because it defines the public surface of a package, but that also means internal file imports can be intentionally blocked. Many resolution bugs are caused by a missing subpath export, a missing default condition, a types branch mismatch or an invalid target.
ExportMap Resolver is deliberately narrower than a full npm package analyzer. It accepts the package.json you already have and one import specifier, then produces a branch-by-branch trace that is easy to paste into an issue, pull request or release checklist.
The tool does not install packages or inspect built files. It checks the map logic and common structural hazards so you know whether the next step is to change package.json, update the import path or run a deeper package publishing audit.