Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postinstall freeze on OSX Yosemite - 10.10.3 #26

Closed
XPilot opened this issue Jul 29, 2015 · 8 comments · Fixed by #114
Closed

Postinstall freeze on OSX Yosemite - 10.10.3 #26

XPilot opened this issue Jul 29, 2015 · 8 comments · Fixed by #114

Comments

@XPilot
Copy link

XPilot commented Jul 29, 2015

When trying to install nw, the download is is ok but when it is running the post install, the process freezes and nothing happens. Error is below:

nw@0.12.2 postinstall /Users/radu.paraschiv/_playground/presentation/NW-Presentation/node_modules/nw
node scripts/install.js

@shama
Copy link
Contributor

shama commented Jul 29, 2015

Hmm could you try npm cache clean and npm i nw again?

Also which version of npm -v? Thanks!

@XPilot
Copy link
Author

XPilot commented Jul 30, 2015

I tried your suggestion, still get the same result.

npm version: 2.5.1
node version: 0.12.7

@saitonakamura
Copy link

Same story here on Windows
npm cache clean didn't help either
Little research shows that the script freezes on var createBar = require('multimeter')(process);
Decomposing it into var multimeter = require('multimeter'); var createBar = multimeter(process); result into successful execute of first line and freeze on second

Node version: 4.4.1
Npm version: 3.8.3

@conceptualspace
Copy link

conceptualspace commented May 30, 2016

it takes it sweet time but eventually does finish (looks like this is just the decompress step and the progress bar is not updated)

tested against nw 0.14.4; osx 10.11.5; npm 3.8.3

@Mithgol
Copy link
Contributor

Mithgol commented Aug 12, 2016

I believe it happens when the site dl.nwjs.io becomes overloaded, especially immediately after every new NW.js release. Once in 2015 it took almost thirty minutes to download and install a new version.

@Mithgol
Copy link
Contributor

Mithgol commented Aug 12, 2016

We could eventually eliminate that central point of failure by switching to some P2P-distributed file system such as IPFS, especially after an implementation of IPFS in JavaScript is finished in the future.

@rohan-deshpande
Copy link

rohan-deshpande commented Jun 4, 2017

Hi,I have a CLI which uses this package and hmm yeah, it's REALLY slow, I've currently been waiting around 20mins and the postinstall is still going.

This wasn't happening a while back when I was building my tool, but it's really frustrating now, any way to improve this?

I'm using npm v5.0.2 now and am on Sierra v10.12, not sure this has anything to do with the issue though...

@Mithgol
Copy link
Contributor

Mithgol commented Jul 12, 2017

The issue seems to be mostly server-side and indicates that dl.nwjs.io is a bit overloaded.

When a version of NW.js is downloaded repeatedly, local caches (such as https://www.npmjs.com/package/install-nw for example) might become helpful, but in other cases only a P2P system might help.

TheJaredWilcurt pushed a commit that referenced this issue Oct 7, 2023
* Refactor install script:
  * Convert from CJS to ESM
  * Improve code documentation
  * Adopt many ES6+ coding styles (let/const, promises, optional chaining, endsWith, etc.)
* Manifest Maintenance:
  * Reduce dependencies from 10 to 5 by swapping most out for native Node modules, or newer alternatives.
  * Updated dependencies.
  * Remove "engines" and "packageManager" from manifest to avoid reported issues.
* Bug fixes:
  * #26 & #74 - Freezing during or after post-install step.
  * #77 - Decompress API change bug. Swapped Decompress for Compressing.
  * #93 - Errors on install and deprecation warnings
  * #109 - Engines/packageManager mismatch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants