How 100 npm packages load on Node.js, Bun, and Deno

By CompatLab ·

97 of 100 frozen npm package versions loaded their root with import on all four pinned runtime profiles. 96 passed the same comparison with require.

Use the CompatLab npm compatibility checker to look up the exact version in your lockfile and see its import and require results.

Loading results

The study attempted 97 exact versions. 97 produced a shared npm dependency tree with lifecycle scripts disabled. 3 frozen rows were declaration or binary distributions outside the module-loading test. Every eligible row has a report.

Root loading outcomes across the frozen 100-version cohort
RuntimeModePassFailOther
Node.js 24.21.0import9703
Node.js 24.21.0require9604
Node.js 26.10.0import9703
Node.js 26.10.0require9604
Bun 1.4.2import9703
Bun 1.4.2require9604
Deno 2.9.7import9703
Deno 2.9.7require9604

Other covers inapplicable entries, preparation limits, incomplete observations, and infrastructure outcomes. The downloads give their individual outcomes. 96 versions had complete planned coverage, including the explicit subpaths that the engine selected.

What showed up

Yargs loaded at the root and failed at its browser entry

yargs 18.2.0 passed all eight root checks. Importing yargs/browser failed on all four profiles. Both Node.js versions reported an unsupported HTTPS module URL. Bun gave no usable diagnostic, and Deno gave different error codes between runs. A fresh rebuild from the retained lock matched the original dependency tree digest and repeated all four failures. This is a browser entry observed in offline server runtimes.

node --input-type=module -e 'await import("yargs/browser")'

View the underlying evidence

estree-walker exposed an import-only root

estree-walker 3.0.3 loaded with import on all four profiles. Its root export provides an import condition and a type declaration. CompatLab recorded all four require cells as inapplicable, so the row contributes to the import result without counting as a require failure.

node --input-type=module -e 'await import("estree-walker")'

View the underlying evidence

tslib loaded at the root with incomplete subpath coverage

tslib 2.9.1 passed both loading modes on every profile. Its export map includes a wildcard and a trailing-slash key. The planner left those paths out and recorded the overall report as inconclusive. An application that uses another tslib path should check that exact path.

node --input-type=module -e 'await import("tslib")'

View the underlying evidence

Method and limits

The frozen cohort ranks 250 candidates from a pinned high-download list using npm counts for November 2–8, 2026. Downloads include transitive installs and CI. The results describe this sample, which skews toward widely used dependencies.

We used npm 11.19.0 with lifecycle scripts disabled and ran on disposable Linux amd64/glibc GitHub runners with network-disabled gVisor execution. Deno ran with -A inside that boundary and used createRequire() for the CommonJS check. Each root ran in a fresh process. Explicit subpaths were checked separately. Wildcard exports were omitted.

Loading evaluates the module. Functional calls, upstream test suites, application behavior, and other operating systems are outside this measurement. Failed entries are observations under this setup. Replay records indicate when a fresh lock-based rebuild produced the same observation.

Download the data