`@cosmjs/stargate` npm install fail due to release 0.28.6 of sub-packages missing
See original GitHub issueRunning npm install @cosmjs/stargate
fails my CI now
Log suggest its due to sub packages @cosmjs/encoding"
and @cosmjs/stream
not found, which do not have a 0.28.6 release on npm yet but is required by @cosmjs/stargate
resolved yarn.lock
"@cosmjs/stargate@^0.28.6":
version "0.28.6"
resolved "https://registry.yarnpkg.com/@cosmjs/stargate/-/stargate-0.28.6.tgz#29dd674dca146aefba8f48886ec5aae0baa641a0"
integrity sha512-72A/qGCt7+1Ce+R53U3SGYllTyJ0JWgewZV/HVcQosVLA+vIf1Pb1Dmd8vd6K2sbb4qdRWaqPHvtjhPUmyrZPQ==
dependencies:
"@confio/ics23" "^0.6.8"
"@cosmjs/amino" "0.28.6"
"@cosmjs/encoding" "0.28.6"
"@cosmjs/math" "0.28.6"
"@cosmjs/proto-signing" "0.28.6"
"@cosmjs/stream" "0.28.6"
"@cosmjs/tendermint-rpc" "0.28.6"
"@cosmjs/utils" "0.28.6"
cosmjs-types "^0.4.0"
long "^4.0.0"
protobufjs "~6.11.3"
xstream "^11.14.0"
CI build log in netlify
5:04:10 PM: Installing NPM modules using NPM version 8.11.0
5:04:10 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
5:04:10 PM: npm WARN config location in the cache, and they are managed by
5:04:10 PM: npm WARN config [`cacache`](http://npm.im/cacache).
5:04:10 PM: npm WARN config tmp This setting is no longer used. npm stores temporary files in a special
5:04:10 PM: npm WARN config location in the cache, and they are managed by
5:04:10 PM: npm WARN config [`cacache`](http://npm.im/cacache).
5:04:19 PM: npm ERR! code ETARGET
5:04:19 PM: npm ERR! notarget No matching version found for @cosmjs/encoding@0.28.6.
5:04:19 PM: npm ERR! notarget In most cases you or one of your dependencies are requesting
5:04:19 PM: npm ERR! notarget a package version that doesn't exist.
5:04:19 PM: Creating deploy upload records
5:04:19 PM: npm ERR! A complete log of this run can be found in:
5:04:19 PM: npm ERR! /opt/buildhome/.npm/_logs/2022-06-09T09_04_10_892Z-debug-0.log
5:04:19 PM: Error during NPM install
5:04:19 PM: Build was terminated: Build script returned non-zero exit code: 1
5:04:19 PM: Failing build: Failed to build site
5:04:19 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1 (https://ntl.fyi/exit-code-1)
5:04:19 PM: Finished processing build request in 16.47341876s
Issue Analytics
- State:
- Created a year ago
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Common errors | npm Docs
You are trying to install on a drive that either has no space, or has no permission to write. Free some disk space...
Read more >Can't install Sharp - node.js - Stack Overflow
I have the same project running on another machine, and there, the install works flawlessly. But on my other machine (both run Linux...
Read more >node-pre-gyp build fail error while installing with npm ... - GitHub
1 error generated. make: *** [Release/obj.target/grpc_node/ext/channel.o] Error 1 gyp ERR! build error gyp ERR ...
Read more >Manage npm packages - Visual Studio (Windows)
Next, you can search for npm packages, select one, and install by selecting Install Package. Install new npm package for esproj. Node.js ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Alright. No answer from npm yet but after trying again the issue magically disappeared today. 0.28.6 and 0.28.7 have been released successfully.
Also has this problem: