From d17ae33f44db02af7e5e5925a653e37053dd1048 Mon Sep 17 00:00:00 2001 From: AdrieanKhisbe Date: Tue, 5 Aug 2025 11:17:35 +0200 Subject: [PATCH] Do not introduce a npm engine when non existing :no_entry: currently, running a bump node to a yarn package cause the introduction of a npm entry. This is not intended and notably breaks heroku deployments --- src/updatees/package.js | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/updatees/package.js b/src/updatees/package.js index 9623f2e3..c03116e6 100644 --- a/src/updatees/package.js +++ b/src/updatees/package.js @@ -37,7 +37,9 @@ const updatePackageEngines = async (node, npm, pkg, {exact = false, loose = true node ? `${prefix ? prefix : getSemverPrefix(existingVersion)}${node}` : existingVersion ), _.update('engines.npm', existingVersion => - npm ? `${prefix ? prefix : getSemverPrefix(existingVersion)}${npm}` : existingVersion + existingVersion && npm + ? `${prefix ? prefix : getSemverPrefix(existingVersion)}${npm}` + : existingVersion ) )(await readPackage(pkg));