Environment
What happened?
Running npm install on the latest main branch fails with ETARGET errors for dependency versions that could not be resolved from the npm registry.
Steps to reproduce
git clone https://github.com/nirholas/XActions.git
cd XActions
npm install
Error
npm ERR! code ETARGET
npm ERR! No matching version found for compression@^1.8.1
After changing compression to 1.7.4, the next installation fails with:
npm ERR! code ETARGET
npm ERR! No matching version found for esbuild@0.28.1
I also verified these versions against the official npm registry:
npm view compression version
# 1.7.4
npm view compression@1.8.1 version
# 404
npm view esbuild version
# 0.23.1
npm view esbuild@0.28.1 version
# 404
What did you expect?
npm install should complete successfully on the latest main branch without requiring manual changes to package.json.
Additional context
To narrow down the issue, I checked out an earlier commit before the recent dependency updates.
Running npm ci on that earlier commit completed successfully, while the latest main branch consistently fails.
This suggests that one or more dependency versions referenced in the current package.json may be incorrect or unavailable on the npm registry.
Thank you for maintaining this project.
Please let me know if I can provide any additional information or test a fix.
Environment
What happened?
Running
npm installon the latestmainbranch fails withETARGETerrors for dependency versions that could not be resolved from the npm registry.Steps to reproduce
git clone https://github.com/nirholas/XActions.git cd XActions npm installError
After changing
compressionto1.7.4, the next installation fails with:I also verified these versions against the official npm registry:
What did you expect?
npm installshould complete successfully on the latestmainbranch without requiring manual changes topackage.json.Additional context
To narrow down the issue, I checked out an earlier commit before the recent dependency updates.
Running
npm cion that earlier commit completed successfully, while the latestmainbranch consistently fails.This suggests that one or more dependency versions referenced in the current
package.jsonmay be incorrect or unavailable on the npm registry.Thank you for maintaining this project.
Please let me know if I can provide any additional information or test a fix.