Node.js 24.21.0
Root importPassed
Root requirePassed
Subpath importsInconclusive1 passed · 1 needs an optional peer
Subpath requiresInconclusive1 passed · 1 needs an optional peer
@supabase/supabase-js2.117.3
Node.js, Bun and Deno compatibility results
Does @supabase/supabase-js 2.117.3 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: mixed results; Deno 2.9.7: inconclusive. Some planned checks are missing or incomplete. Loading success does not establish functional correctness or package safety.
Observed 2026-10-09 14:58 UTC · Linux amd64 / glibc
Loading results
| Runtime | Root import | Root require | Subpath imports | Subpath requires |
|---|---|---|---|---|
| Node.js24.21.0 | Passed | Passed | Inconclusive1 passed · 1 needs an optional peer | Inconclusive1 passed · 1 needs an optional peer |
| Node.js26.10.0 | Passed | Passed | Inconclusive1 passed · 1 needs an optional peer | Inconclusive1 passed · 1 needs an optional peer |
| Bun1.4.2 | Passed | Passed | Mixed results1 passed · 1 failed | Mixed results1 passed · 1 failed |
| Deno2.9.7 | Passed | Passed | Inconclusive1 passed · 1 needs an optional peer | Inconclusive1 passed · 1 needs an optional peer |
Node.js 26.10.0
Root importPassed
Root requirePassed
Subpath importsInconclusive1 passed · 1 needs an optional peer
Subpath requiresInconclusive1 passed · 1 needs an optional peer
Bun 1.4.2
Root importPassed
Root requirePassed
Subpath importsMixed results1 passed · 1 failed
Subpath requiresMixed results1 passed · 1 failed
Deno 2.9.7
Root importPassed
Root requirePassed
Subpath importsInconclusive1 passed · 1 needs an optional peer
Subpath requiresInconclusive1 passed · 1 needs an optional peer
Import uses ESM; require uses CommonJS. Results cover the package root and selected explicit subpaths. Select a result to inspect its evidence.
Does @supabase/supabase-js work in Node.js, Bun and Deno?
Coverage is limited: some exports or checks were omitted, incomplete or unavailable. A passing runtime row does not remove those gaps. 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 @supabase/supabase-js work with Node.js?
@supabase/supabase-js@2.117.3 has inconclusive loading evidence in Node.js 24.21.0. 4 passed · 0 failed · 2 need optional peers.
@supabase/supabase-js@2.117.3 has inconclusive loading evidence in Node.js 26.10.0. 4 passed · 0 failed · 2 need optional peers.
Does @supabase/supabase-js work with Bun?
@supabase/supabase-js@2.117.3 had mixed loading results in Bun 1.4.2. 4 passed · 2 failed.
Does @supabase/supabase-js work with Deno?
@supabase/supabase-js@2.117.3 has inconclusive loading evidence in Deno 2.9.7. 4 passed · 0 failed · 2 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.