Closed standbyoneself closed 3 years ago
You might look at the run-if-changed
field in package.json
. run-if-changed
is intended to help force commands when files change, such as an npm install when there is a new commit with a change to the package-lock.
So I think there could be some recursion if a changed file (e.g., as we have had in the main branch for package-lock.json
) causes an install (esp. if there is also a prepare
script). I'm not working with the code now, so can't really say more about whether it applies, but wanted to mention in case that's what was going on.
not sure. can you rebuild node_modules from scratch with npm ci?
I believe I found the issue. You have a wrong .npmrc (that was required when the repo was private). I deleted it, rebuild the package and this seems to work... Let me know if this is OK for you.
Waiting for 10 minutes has changed nothing.
Any help?