← Package details

Runtime evidence / smoke tested

@tanstack/react-start1.168.60

Observed 2026-10-08 20:59 UTC · Linux amd64 / glibc

Download JSON
Immutable loading evidence badge for @tanstack/react-start
Mixed results

All applicable planned loading observations completed.

This is loading evidence. It does not establish functional correctness or package safety.

Runtime matrix

4 pinned runtimes · production_56d463b6f06722afc008ed99fb1a0179

Import uses ESM; require uses CommonJS. Root modes use fresh sandboxes. Subpath batches share module caches and globals. Select a result to inspect its evidence.

Does @tanstack/react-start 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 @tanstack/react-start work with Node.js?

@tanstack/react-start@1.168.60 had mixed loading results in Node.js 24.21.0. 11 passed · 6 failed.

@tanstack/react-start@1.168.60 had mixed loading results in Node.js 26.10.0. 11 passed · 6 failed.

Does @tanstack/react-start work with Bun?

@tanstack/react-start@1.168.60 had mixed loading results in Bun 1.4.2. 11 passed · 6 failed.

Does @tanstack/react-start work with Deno?

@tanstack/react-start@1.168.60 had mixed loading results in Deno 2.9.7. 11 passed · 6 failed.

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

Shared preparation

Passed

98 installed packages · 10 optional dependencies omitted · lifecycle scripts disabled

The omitted count covers locked optional dependencies. Optional peers are separate and are not automatically installed.

Static manifest, native and script observations

Static indicators are context; their presence alone does not establish a prerequisite or failure.

Coverage and evidence

Node.js 24.21.0 · Root · ESM importPassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON
Node.js 24.21.0 · Root · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON
Node.js 24.21.0 · Subpaths · ESM importMixed results

10 passed · 6 failed · 16 observed of 16 planned

package_resolution_failed · module resolution
Cannot find package 'vite' imported from /workspace/node_modules/@tanstack/start-plugin-core/dist/esm/vite/import-protection-plugin/plugin.js

Evidence JSON
Node.js 24.21.0 · Subpaths · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON
Node.js 26.10.0 · Root · ESM importPassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON
Node.js 26.10.0 · Root · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON
Node.js 26.10.0 · Subpaths · ESM importMixed results

10 passed · 6 failed · 16 observed of 16 planned

package_resolution_failed · module resolution
Cannot find package 'vite' imported from /workspace/node_modules/@tanstack/start-plugin-core/dist/esm/vite/import-protection-plugin/plugin.js

Evidence JSON
Node.js 26.10.0 · Subpaths · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON
Bun 1.4.2 · Root · ESM importPassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON
Bun 1.4.2 · Root · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON
Bun 1.4.2 · Subpaths · ESM importMixed results

10 passed · 6 failed · 16 observed of 16 planned

esm_import_failed · module evaluation
No error message was captured. The cause of this loading failure is unknown.

Evidence JSON
Bun 1.4.2 · Subpaths · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON
Deno 2.9.7 · Root · ESM importPassed

1 passed · 0 failed · 1 observed of 1 planned

Evidence JSON
Deno 2.9.7 · Root · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON
Deno 2.9.7 · Subpaths · ESM importMixed results

10 passed · 6 failed · 16 observed of 16 planned

package_resolution_failed · module resolution
Could not find package 'vite' from referrer 'file:///workspace/node_modules/@tanstack/start-plugin-core/dist/esm/vite/import-protection-plugin/plugin.js'.

Evidence JSON
Deno 2.9.7 · Subpaths · CommonJS requireNot applicable

0 passed · 0 failed · 0 observed of 0 planned

Evidence JSON
Planner omissions
pattern
0
non executable
1
not exported
0
invalid subpath
0
coverage limit
0
  • ./package.json — non executable

Reproduce these inputs

Download the recorded inputs and exact dependency lock. These files do not include the CLI, runtime images or installed packages.

Local replay requires setup. The CLI currently runs from the CompatLab source repository on a qualified Linux amd64/runsc host. Hosted runtime images are not yet distributed for public download; an operator must supply the exact images named in this report. A fresh image build does not substitute for them. CLI setup and replay requirements

Command for a configured host

Run from the built CompatLab repository with both downloads in that directory and the exact runtime images loaded. Rebuilding creates a new snapshot generation.

sudo "$(command -v node)" apps/cli/dist/bin.js reproduce ./53ec3efc-7765-450b-a3c3-48010e409073-reproduction.json --rebuild --lockfile ./package-lock.json --json

The original worker last reported its sealed snapshot as available. Verified reuse requires those actual bytes in your local state directory.

Exact provenance
artifact
@tanstack/react-start@1.168.60
integrity
sha512-WMOM0Xlh2lPbVlbjYM6uOxOpiaWRPvODm/dwkLsGKq5tjyHOHZmKckJgwlrZl7OQUqFlOZHYj8bKUTgoeg8cUQ==
tarball
https://registry.npmjs.org/@tanstack/react-start/-/react-start-1.168.60.tgz
snapshot
a775fbea-0075-4125-9c82-0b511600a1a8
generation
f563f7df-20a4-4ba6-9e4e-35d32f6184db
lockDigest
f6402c118b3bd36479242b760987226c0679d4cdfde4bf70089b8d7277a47989
treeDigest
e593d49598320dff349b2bc971ad0d0f069877e0cf224ff68851d24196d261ba
installerImage
node:24.21.0-bookworm-slim@sha256:5cbc7caba8c2c0f0bca675d1b61b9f2857e1cf1853c6164ee9dd409501a936e7
preparationProfile
npm_11_19_0_linux_amd64_v2
harness
load_v2
planner
explicit_exports_v1
policy
runtime_limits_v2
classifier
classifier_v1
classifiedAt
2026-10-08T20:59:20.739Z

node_24_21_0

sha256:5023d2ff993649ea7c5d8e2360ba8b8256488ec3cec9b7b3edd4d0261b641778

Built 2026-10-04 15:20 UTC · runtime_image_v1

node_26_10_0

sha256:6fd2353d7583d6c98e540d32b8c7c6e8b345d3d55056221eb24dd05cfd15f6eb

Built 2026-10-04 15:20 UTC · runtime_image_v1

bun_1_4_2

sha256:f7ed957f11f06db3be00760147a186e7e66e6a431204d3d591e5a282ef1aadef

Built 2026-10-04 15:21 UTC · runtime_image_v1

deno_2_9_7

sha256:0441484bc07f45de2c9d37971931dba8ece8e3854fb4fb7f004eca8b1aa5263f

Built 2026-10-04 15:21 UTC · runtime_image_v1

Evidence limitations

  • 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.