Gulp CLI and Local Gulp Package: Interoperability After a Failed Upgrade

Answer first

No. The gulp CLI does not automatically create a backup of gulpfile.js or node_modules before upgrading the local gulp package, and it should not be expected to. Package upgrades are the responsibility of the package manager, not the CLI. There is no built-in rollback path in gulp tooling.

Confirmed facts

The gulp CLI resolves the gulp package from the project's node_modules. If a local version exists, that version is used; a global CLI only falls back when no local version is present. Node module resolution precedence means a broken or missing local install blocks task execution directly.

A failed local gulp upgrade can leave the project without a loadable gulp module, producing "Cannot find module gulp" errors, or it can leave an older API installed while the gulpfile uses newer syntax, producing runtime errors.

Likely explanation vs uncertainty

It is likely that the current unusable state is a version mismatch between the CLI expectation and the locally installed gulp package after an interrupted upgrade. This is consistent with how resolution works.

Uncertainty remains about whether an automatic backup of gulpfile.js and node_modules would be desirable. Backup strategies are not built into gulp. Creating and managing node_modules snapshots would be heavy, package-manager specific, and outside gulp's scope. Manual npm/yarn/pnpm install and version pinning is the typical recovery.

Steps needed for this case

1. Verify resolution. Run gulp --version in the project root and compare the reported local gulp version to the version in package.json devDependencies.
2. Verify the local module loads. Run node -e "require('gulp')" in the project directory. Failure confirms a corrupted or missing local package.
3. Check actual installed version. Inspect node_modules/gulp/package.json version field against package.json.
4. Restore a consistent local install with the package manager you use, e.g. npm ci or rm -rf node_modules package-lock.json && npm install, then re-run the version checks.

If you want a manual safety net for future upgrades, pin the gulp version in devDependencies, commit package-lock.json, and keep a version-controlled copy of gulpfile.js. That provides rollback without CLI involvement.

One missing diagnostic detail that changes the recommendation: which package manager was used for the upgrade and whether the gulpfile uses gulp v4 series API. That determines whether a simple reinstall is sufficient or an API compatibility fix is also required.