EnvTrail: compare Node.js environments without recording secret values
“It works on my machine” usually leads to a few questions: Which Node version? Did the lockfile change? Is a variable missing from .env ? I made EnvTrail to put those checks in one comparison. Save a snapshot where the project works, then compare it with another machine. The output is a terminal summary or a standalone HTML report. Here's an example report with synthetic data. No installation…
The EnvTrail tool enables developers to compare Node.js environments on different machines without recording any secret values. By saving a snapshot of a working project and comparing it to another machine's environment, users can identify discrepancies in the Node.js runtime, package versions, lockfile fingerprints, and environment variables.
The comparison produces a terminal summary or an HTML report, which can be viewed offline without any external assets or telemetry. EnvTrail runs locally, checking the Node.js version, system npm, pnpm, Yarn, and Bun versions, lockfile fingerprints, and declared environment variables in .env.example files. It does not save the actual values of environment variables or lockfiles, ensuring privacy.
Users should review the output before sharing it. Although EnvTrail identifies differences, it cannot determine the root cause of any issues. The tool is written in JavaScript, released under the MIT license, and its code is hosted on GitHub. Feedback on confusing comparisons or additional checks is appreciated.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
