EnvTrail
Environment diagnostics
Offline HTML report

Report / Baseline → current

Environment comparison

Action required

Resolve the unmet requirements below, then capture the current environment again.

3 blocking6 warnings0 notes2 snapshots All times UTC

Runtime & environment

Baseline vs. current
Runtime and environment overview in the baseline and current snapshots. Changed values are marked with an amber dot.
EnvironmentBaselineCurrent
Node.js22.20.024.15.0
npm10.9.311.12.1
Systemdarwin / arm64win32 / x64
Required keys2 / 2 present1 / 2 present
Baseline captured
Current captured

Resolve first

3 next steps
  1. node does not meet the project requirement

    Select a node version that satisfies >=22 <23 and capture the environment again.

  2. Required variable DATABASE_URL is absent

    Configure DATABASE_URL locally without committing its value, then capture again.

  3. Node does not match .nvmrc

    Select the Node version declared by .nvmrc and capture the environment again.

Findings9

Blocking differences first

Blocking

node does not meet the project requirement

ENGINE_MISMATCH

package.json engines.node requires >=22 <23; the current version is 24.15.0.

Suggested next step

Select a node version that satisfies >=22 <23 and capture the environment again.

Blocking

Required variable DATABASE_URL is absent

ENV_MISSING

DATABASE_URL is declared in an environment example, but was not found in the process environment or a local .env file.

Suggested next step

Configure DATABASE_URL locally without committing its value, then capture again.

Blocking

Node does not match .nvmrc

NODE_VERSION_MISMATCH

.nvmrc specifies 22.20.0; the current Node version is 24.15.0.

Suggested next step

Select the Node version declared by .nvmrc and capture the environment again.

Warning

CPU architectures differ

ARCHITECTURE_DIFFERENT

Baseline: arm64. Current: x64. Native dependencies or platform-specific behavior may differ.

Suggested next step

Check whether the project and its native dependencies support both environments.

Warning

package-lock.json contents differ

LOCKFILE_CHANGED

SHA-256 differs between snapshots (aaaaaaaaaaaa → bbbbbbbbbbbb). This shows different lockfile bytes, not which dependency changed.

Suggested next step

Compare the lockfile in Git and install dependencies with the intended frozen or clean install command.

Warning

The npm system probe differs from the project pin

PACKAGE_MANAGER_MISMATCH

package.json packageManager specifies npm@10.9.3; the system/offline probe detected 11.12.1. Project-specific selection was not executed or verified. A project override may already select the pinned version.

Suggested next step

Verify the npm version selected inside this project against 10.9.3 before changing its installation or configuration.

Warning

Operating systems differ

PLATFORM_DIFFERENT

Baseline: darwin. Current: win32. Native dependencies or platform-specific behavior may differ.

Suggested next step

Check whether the project and its native dependencies support both environments.

Warning

node versions differ

RUNTIME_VERSION_DIFFERENT

Baseline: 22.20.0. Current: 24.15.0. A version difference alone does not establish incompatibility.

Suggested next step

Use the project's declared node version where available, then reproduce the issue.

Warning

npm versions differ

RUNTIME_VERSION_DIFFERENT

Baseline: 10.9.3. Current: 11.12.1. A version difference alone does not establish incompatibility. These are system/offline probes; project-specific selection was not executed or verified.

Suggested next step

Use the project's declared npm version where available, then reproduce the issue.

Environment details

Changed value
Selected environment metadata in the baseline and current snapshots. Changed values are marked with an amber dot.
Environment detailBaselineCurrent
Node.js22.20.024.15.0
npm10.9.311.12.1
Systemdarwin / arm64win32 / x64
Project package managernpm@10.9.3npm@10.9.3
Node.js requirement>=22 <23>=22 <23
.nvmrc22.20.022.20.0
Required keys2 / 2 present1 / 2 present
package-lock.jsonSHA-256 aaaaaaaaaaaa…SHA-256 bbbbbbbbbbbb…

Requirement checks use the current snapshot. A difference alone does not establish incompatibility.

Sharing & privacy

Self-contained · Works offline

What this report includes

EnvTrail compares selected environment metadata. It never embeds a complete snapshot or reads environment-variable values into this report.

Included when available

  • Runtime and package-manager versions
  • Operating system and CPU architecture
  • Declared project tool requirements
  • Environment-variable names and presence
  • Lockfile comparison results

Excluded

  • Environment-variable values
  • Absolute project and home paths
  • Source code and file contents
  • Remote scripts, fonts, and tracking

Review names and metadata before sharing: project requirements and environment-variable names can still reveal context about your project. This report is a diagnostic aid, not a guarantee of identical application behavior.