-
Notifications
You must be signed in to change notification settings - Fork 27
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
Silent fail on postInstall #29
Comments
what is your version of nodejs please ? |
Please also provide your npm version! |
node -v npm -v |
Can you try the following commands? npm i -g npm@latest
rd /s /q node_modules
npm -v
npm i It should update npm and try to reinstall the dependencies. |
Can't play the rd command, (command not found). |
Anything else that delete the directory is ok. Le vendredi 17 avril 2015, ki7 [email protected] a écrit :
Florent Cailhol |
Well Still.
|
Upgraded Le jeudi 16 avril 2015, Maxime Thirouin [email protected] a écrit :
|
So does this fix anyting ? |
Absolutely not /o. I'm still looking for the why a postinstall scripts is not executed in the meantime. |
Can you clone this repo and run the tests ? |
:$ Should have been my first move. and the test passes... |
Well, this more a gulp-cssnext issue? |
the thing is, there is a test to know if we are in dev or in non dev Line 30 in f7f552d
maybe that's the problem |
I got a similar issue https://travis-ci.org/putaindecode/putaindecode.fr/builds/60327539 |
I were having issues ("blocked" install - see build lined above) so I tried to make a more node friendly approch (without eval) in the We will see on this project if the issue happen again and we might eventually merge the changes of the branch (not the branch directly since I got to add dist/ in git to get npm install working from git repo) if no problems came up. So wait and see. |
Well well wel... https://travis-ci.org/putaindecode/putaindecode.fr/builds/60335395 |
Not sure if this module is responsible. |
We're experiencing the same issue with a build in our CI system (Bamboo). It reaches the post-install and then hangs. It seems to happen sporadically and only happens in CI. I haven't seen it happen locally yet. Logs are below.
|
I 've activated --loglevel=info for npm install on several place, hopes that helps to find what is happening :/ |
@mark-adams do you still get the issue recently ? |
Closing has nobody complained about this. Maybe track #32. |
I just started running into this issue... my CI server consistently fails silently when installing this package (as an indirect dep of postcss-cssnext). I'm using [email protected] and [email protected]. Any thoughts?
|
No clue. I think it's time to remove the generation step. |
Closed by #47 |
The postInstall scripts seems to never be executed.
it fails leaving stderout with
d1b2d11#commitcomment-10753523
The text was updated successfully, but these errors were encountered: