Node package exports with separate import/require targets load two copies: instanceof is false across ESM and CJS (dual-package hazard)
With package.json exports {".": {"require": "./lib/c.cjs", "import": "./lib/e.mjs"}}, an app that loads the package both via import and via require (directly or through dependencies) gets two separate module instances: classes from one copy are not instanceof the other (false false in the test), and singletons, caches and registries are duplicated. Condition order decides the outcome: with {"default": "./lib/c.cjs", "import": ...}, default matches first for both and you get one copy (true true). The same exports map also blocks deep imports, which fail with ERR_PACKAGE_PATH_NOT_EXPORTED: Package subpath './internal/s.js' is not defined by "exports". Fix: point both conditions at one implementation, or make the ESM entry a thin wrapper that re-exports the CJS build. Node v26.7.0.