-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Use 'node-exit' for better windows support #172
Comments
strongly 👎, it destroys |
Yea, it is not ideal at all. But stdout on windows is truncating (same as in the grunt issue), so this will come back again if It is time it is fixed upstream in node itself. Bug is open for 2 years now.. 😞 |
Gulp doesn't have a goal to support Windows. I think this should be closed. |
@phated to an extent - if an easy fix can be put in place that doesn't penalize others I would do it. node-exit breaks things on other OSes though apparently |
I can live without node-exit, it is a huge hack after all. With some luck this gets fixed upstream before 0.12. But I'm sure this is a misunderstanding that Gulp doesn't support Windows? If you look at the known issue I mentioned you can see windows support in node.js is a real thing. Grunt can do it so I'd expect Gulp to do so too. |
Huh, why wouldn't gulp support Windows? |
Calm down @Bartvds and @thasmo. As @contra said, Gulp will take patches for windows as long as they don't cause problems on other OSes. @robrich, a core contributor, uses windows, so it will continue to work for the foreseeable future. I was just stating that Gulp hasn't made it a goal to work 100% (like truncating stdout on exit) on windows over other OSes. This issue in particular should be fixed upstream. Sorry for the confusion. |
I agree. Though Windows support is near and dear to me (I think gulp fills the void left by nant and not filled by MSBuild) making everyone suffer isn't a good move. Let's push to have this resolved in node, not hacked around in gulp. |
well, it's just putting the suffering on us developers having to support Windows :p |
Cool, we'll see if node fixes this (one day..). Re windows: if people not reinvent system stuff but use modules then things 2014/1/21 Sindre Sorhus notifications@github.com
|
Node.js has a known issue on windows with truncated stdout on process exit.
I have this now when using
gulp
within WebStorm.The grunt team made a nice hack for it: I propose to use this in gulp: node-exit
The text was updated successfully, but these errors were encountered: