Your Terminal Says Node 22. A Bun Script Says Node 26. Neither Is Lying.
If a tutorial, a scaffolder or an AI agent put Bun on your machine, the mismatched version numbers aren’t a bug — and one line tells you which runtime is really running your file.
Bun landed on your machine somehow — you, a scaffolder, or an AI agent — and now `node -v` and a Bun-run script disagree about which version of Node you’re on. Nothing is broken. This shows, in about three minutes on Bun 1.4.2 and Node 22.22, why Bun reports a Node-shaped version on purpose, the single line (`process.versions.bun`) that tells you what’s actually executing your code, and the two-lockfile trap that costs real time.
Read more


























