Package Exports Resolution Workbench

How to use Package Exports Resolution Workbench

Trace package.json export selection for a concrete subpath and an explicit set of active conditions. Follow insertion-ordered conditions, exact keys, the most specific single-asterisk pattern and bounded array alternatives. A chosen target is a static mapping result, not proof that the file exists or loads.

1. Provide complete package.json json, requested package subpath, active condition names as a json array.
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

• 100 KB of JSON, 40 parsed levels, 500 export keys, 2,000 visited target values, 20 resolution levels and 32 supplied conditions. Prototype-related JSON keys are refused.
• The selection model is pinned to Node.js 24.14.0 source behavior. Arrays skip invalid-target alternatives and null alternatives; a conditional null blocks that branch. Condition order comes from the supplied JSON object.
• The file-path profile is stricter than every Node legacy/deprecated allowance: no empty/dot/parent/node_modules segments, query, fragment, backslash, encoded separator, non-ASCII or trailing slash. A pattern key contains at most one asterisk.
• A null or missing top-level exports field has no active exports map; legacy resolution is not attempted. No main fallback, package imports, filesystem lookup, module execution or dependency download occurs.
• Inputs are processed on this device and are not automatically saved or uploaded.