From 041a57747af817f584b5a1fac61440bf8083c1f6 Mon Sep 17 00:00:00 2001 From: Jordan Harband Date: Thu, 2 Jul 2026 14:35:57 -0500 Subject: [PATCH] [Tests] `installation_node`: use a published `is-nan` version `is-nan@1.0.0` was published on 2014-07-05 and unpublished minutes later (the registry's `time` map still lists it, but `versions` jumps from `0.0.0` to `1.0.1`), so `npm install -g is-nan@1.0.0` fails with `ETARGET`, and the regression test added in ce157343 fails deterministically in every shell. See https://github.com/nvm-sh/nvm/actions/runs/28407118533 --- test/installation_node/install while reinstalling packages | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/test/installation_node/install while reinstalling packages b/test/installation_node/install while reinstalling packages index 0328eb51..1e92ddb2 100755 --- a/test/installation_node/install while reinstalling packages +++ b/test/installation_node/install while reinstalling packages @@ -72,7 +72,7 @@ npm list --global | grep object-is > /dev/null || die "object-is isn't installed # install a fresh global package on the source (v9.7.0) only nvm use 9.7.0 -npm install -g is-nan@1.0.0 || die "npm install -g is-nan failed" +npm install -g is-nan@1.0.1 || die "npm install -g is-nan failed" npm list --global | grep is-nan > /dev/null || die "is-nan isn't installed on v9.7.0" # precondition: the already-installed target (v9.10.0) must not have it yet