Choose a version or request a scan

@convex-dev/agent0.7.3

Node.js, Bun and Deno compatibility results

Does @convex-dev/agent 0.7.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. All applicable planned checks completed. Loading success does not establish functional correctness or package safety.

Observed 2026-10-05 11:22 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 @convex-dev/agent 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 @convex-dev/agent work with Node.js?

@convex-dev/agent@0.7.3 has inconclusive loading evidence in Node.js 24.21.0. 8 passed · 2 failed · 2 need optional peers.

@convex-dev/agent@0.7.3 has inconclusive loading evidence in Node.js 26.10.0. 8 passed · 2 failed · 2 need optional peers.

Does @convex-dev/agent work with Bun?

@convex-dev/agent@0.7.3 had mixed loading results in Bun 1.4.2. 8 passed · 4 failed.

Does @convex-dev/agent work with Deno?

@convex-dev/agent@0.7.3 has inconclusive loading evidence in Deno 2.9.7. 8 passed · 2 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_56d463b6f06722afc008ed99fb1a0179 · 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