Error could not find semver
See original GitHub issueI’ve just started getting the following error when using this:
Error: Could not find file '/home/runner/work/_actions/_temp_048ce8a4-bb03-49f4-855e-1f0b02f1614b/_staging/r0adkll-sign-android-release-d28dc26/node_modules/jest-snapshot/node_modules/.bin/semver'.
I believe ff34f681c113c5965a5b44406bf0033326f29886 is the culprit, it appears semver was completely removed.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Npm install cannot find module 'semver'
Solution:Delete the npm-cache/npm folder in the installation directory of nodejs. In windows, it is in C:/User/Username/Appdata/Roaming/npm(or npm_cache). and ...
Read more >Npm can't find module "semver" error in Ubuntu 19.04
It asked me to run command 'npm ci' from which I started getting this error. I tried reinstalling npm but it won't work....
Read more >Fix - Cannot find module 'semver' error in Node.js
The Cannot find module 'semver' error occurs if you're trying to run an npm install command in your project. To solve the error...
Read more >Fix for Cannot Find Module 'Semver' on Ubuntu 20.04 #125
Fix for Cannot Find Module 'Semver' on Ubuntu 20.04 I was unable to run npm run setup --silent and npm run dev until...
Read more >All the Ubuntu error troubles I experienced | by Shawn Choi
It throw me an error that says Cannot find module 'semver' after update my npm using npm update -g. npm install (with no...
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
okay, I’ve merged your PR, updated dependencies, re-built src, and made sure the latest
node_modules
were added. That should hopefully resolve this issue. I have also tagged and released this underv1.0.3
so @tmorone-rezi you can start referring to stable versions/tags.I appreciate everyone’s patience and I’m sorry for the inconvenience! (Typescript/Web is not my main discipline 😆 )
Use this until it gets fixed:
uses: r0adkll/sign-android-release@21072f7435f485b65555103ff2c60e86560b759e
Adding release tags to stable versions would be a good practice. Thanks for maintaining this package!