Choose a version or request a scan

preact11.0.1

Node.js, Bun and Deno compatibility results

Does preact 11.0.1 load in Node.js, Bun and Deno? In the recorded environment, the results were Node.js 24.21.0: inconclusive; Node.js 26.10.0: inconclusive; Bun 1.4.2: inconclusive; Deno 2.9.7: inconclusive. All applicable planned checks completed. Loading success does not establish functional correctness or package safety.

Observed 2026-10-09 11:10 UTC · Linux amd64 / glibc

Loading results

Import uses ESM; require uses CommonJS. Results cover the package root and selected explicit subpaths. Select a result to inspect its evidence.

Does preact work in Node.js, Bun and Deno?

All applicable planned loading checks completed. The runtimes used the same installed dependency snapshot. Test environment: Linux amd64 / glibc, with install scripts and execution networking disabled. Successful import or require does not prove that package functions, native features or your application work.

Does preact work with Node.js?

preact@11.0.1 has inconclusive loading evidence in Node.js 24.21.0. 26 passed · 0 failed · 4 need optional peers.

preact@11.0.1 has inconclusive loading evidence in Node.js 26.10.0. 26 passed · 0 failed · 4 need optional peers.

Does preact work with Bun?

preact@11.0.1 has inconclusive loading evidence in Bun 1.4.2. 26 passed · 3 failed · 1 needs an optional peer.

Does preact work with Deno?

preact@11.0.1 has inconclusive loading evidence in Deno 2.9.7. 26 passed · 0 failed · 4 need optional peers.

Compare npm package compatibility across Node.js, Bun and Deno · Browse observed runtime loading failures

Source evidence and limitations

This page selects an eligible observation for this exact version, preferring the current environment. The selection can change after a rescan or reclassification. Cite the observation link below when referring to these results.

Matrix production_ab51508deb208994caf81cb80f14b800 · Classifier classifier_v2 · Install scripts disabled

  • Only installation and loading were observed; functional correctness and package safety are not established.
  • Subpath batches share module caches and globals; root modes use separate fresh sandboxes.
  • Package-visible harness observations can be tampered with. They are not adversarial attestation.
  • Evidence applies to these exact artifacts, dependency snapshot, runtime images and Linux amd64/glibc policy.
  • Runtime error codes are captured observations and can also be thrown by package code.
How the tests work