installation error
See original GitHub issue➜ test git:(master) ✗ npm i i18n --save
> typechecker@2.0.8 preinstall /Applications/MAMP/htdocs/test/node_modules/extendr/node_modules/typechecker
> node ./cyclic.js
npm ERR! Cannot read property 'pause' of undefined
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/steeply/.npm/_logs/2017-08-28T08_06_17_854Z-debug.log
➜ test git:(master) ✗ node -v && npm -v
v8.4.0
5.4.0
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (2 by maintainers)
Top Results From Across the Web
How to troubleshoot Windows Installer errors - Microsoft Support
Describes how to troubleshoot problems that occur when you install, uninstall, or upgrade a program on a Windows-based computer by using Windows Installer....
Read more >How to Fix Microsoft Windows 10 Installation Error Codes
This document covers the list of Windows 10 installation error codes with its corresponding Cause and Resolution. Learn how to Fix!
Read more >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 >Fix problems installing Chrome - Google Chrome Help
If you get an error message when you try to download and install Google Chrome, try these fixes. Fix most installation errors Make...
Read more >9 Ways to Fix an Error Occurred While Preparing the Installation
"While installing the macOS I am repeatedly getting the following error: "An error occurred while preparing the installation el Capitan." I have ...
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
Node 8.8.1 bundle 5.4.2. The workaround that I work for me is:
in my package.json. In think that is not perfect solution, but works 😉
I am about to update all deps and also drop some support for legacy node versions - but 1st some PRs need to get merged