Engines.node field behavior when Glitch upgrades Node.js from 16 to 18
Developers want Glitch projects to automatically respect the Node.js version range declared in the engines.node field of package.json, so that native modules built for a specific major version continue to work after a platform‑wide Node.js rollout. Currently Glitch provisions the latest default Node.js (v18) regardless of the declared range, shows the actual
glitch