[Solved] Error install flow-typed on Mac OS 10.11.6
See original GitHub issue$ npm i flow-typed@2.0.0-beta.9 -g
npm WARN deprecated lodash.assign@4.2.0: This package is deprecated. Use Object.assign.
> nodegit@0.15.1 preinstall /Users/sean/.nvm/versions/node/v6.6.0/lib/node_modules/.staging/nodegit-af44277b
> node lifecycleScripts/preinstall
[nodegit] Running pre-install script
[nodegit] Configuring libssh2.
{ Error: Command failed: /Users/sean/.nvm/versions/node/v6.6.0/lib/node_modules/.staging/nodegit-af44277b/vendor/libssh2/configure --with-libssl-prefix=/Users/sean/.nvm/versions/node/v6.6.0/lib/node_modules/.staging/nodegit-af44277b/vendor/openssl/openssl
configure: error: cannot find OpenSSL or Libgcrypt,
try --with-libssl-prefix=PATH or --with-libgcrypt-prefix=PATH
at ChildProcess.exithandler (child_process.js:206:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:877:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
killed: false,
code: 1,
signal: null,
cmd: '/Users/sean/.nvm/versions/node/v6.6.0/lib/node_modules/.staging/nodegit-af44277b/vendor/libssh2/configure --with-libssl-prefix=/Users/sean/.nvm/versions/node/v6.6.0/lib/node_modules/.staging/nodegit-af44277b/vendor/openssl/openssl' }
configure: error: cannot find OpenSSL or Libgcrypt,
try --with-libssl-prefix=PATH or --with-libgcrypt-prefix=PATH
[nodegit] ERROR - Could not finish preinstall
{ Error: Command failed: /Users/sean/.nvm/versions/node/v6.6.0/lib/node_modules/.staging/nodegit-af44277b/vendor/libssh2/configure --with-libssl-prefix=/Users/sean/.nvm/versions/node/v6.6.0/lib/node_modules/.staging/nodegit-af44277b/vendor/openssl/openssl
configure: error: cannot find OpenSSL or Libgcrypt,
try --with-libssl-prefix=PATH or --with-libgcrypt-prefix=PATH
at ChildProcess.exithandler (child_process.js:206:12)
at emitTwo (events.js:106:13)
at ChildProcess.emit (events.js:191:7)
at maybeClose (internal/child_process.js:877:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
killed: false,
code: 1,
signal: null,
cmd: '/Users/sean/.nvm/versions/node/v6.6.0/lib/node_modules/.staging/nodegit-af44277b/vendor/libssh2/configure --with-libssl-prefix=/Users/sean/.nvm/versions/node/v6.6.0/lib/node_modules/.staging/nodegit-af44277b/vendor/openssl/openssl' }
/Users/sean/.nvm/versions/node/v6.6.0/lib
└── (empty)
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
If an error occurred while updating or installing macOS
The message might say that an error occurred while downloading, preparing, or installing, or that the installer is damaged or could not be ......
Read more >9 Ways to Fix an Error Occurred While Preparing the Installation
Fix 1: Restart your Mac The first step when you see an error occurred while preparing the installation sierra is to restart your...
Read more >OS X El Capitan Won't Install! Why? - Krazy Ken's ... - YouTube
OS X El Capitan won't install on these two MacBook Pros (8,1). Why? Let's find out! ... Your browser can't play this video....
Read more >El Capitan: No packages were eligible for install-Fix - YouTube
Fixes the " install failed" and "No packages were eligible for install " error while installing macOS El Capitan with Internet Recovery by ......
Read more >Fixing Mac OS X Install Errors “can't be verified ... - OSXDaily
To determine if the Terminal date trick can fix those error messages and help you to successfully install MacOS X, you'll need to...
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
Thanks, @ctrlplusb. I think this would be a good thing to go into an FAQs section of the README. I’ll add this there and then close this out
Ok, I’ve added an FAQs section over here with this issue listed.
Thanks again for the report!