Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[now-cli] Error after upgrading to 16.3.0
See original GitHub issueReceive an error message/unable to deploy after upgrading now-cli to version 16.3.0.
Works okay when reverting back to 16.2.0
Details:
-
Upgrade to 16.3.0 with
npm i -g now@latest -
In console, run “now” command
now -
Get this error:
Error! ENOENT: no such file or directory, stat ‘LOCAL_PATH/mobile/node_modules/.bin/detect-libc’
The ‘LOCAL_PATH/mobile’ is the directory for a react-native version in the same repo.
-
Revert back to 16.2.0
npm i -g now@16.2.0 -
In console, run “now” command
now -
Runs and deploys correctly without errors
I was able to recreate these steps several times.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi, it worked! Was able to do one deployment with the canary version.
I should have mentioned that my client environment is Ubuntu 16.04 LTS, so probably not the norm. Thanks!!!
Thanks for the update! It seems this is only affecting some machines because I was unable to reproduce but @sophearak was able to reproduce.
We released a fix to the canary channel that should resolve this problem.
Can you try
npm i -g now@canaryto confirm this this solves your issue? Thanks!