-
Notifications
You must be signed in to change notification settings - Fork 7
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
Issue on Linux with '/dev/stdin' "can't open". #3
base: master
Are you sure you want to change the base?
Issue on Linux with '/dev/stdin' "can't open". #3
Conversation
We need to stick to Anyway, it seems a bug. Thanks for reporting!
|
It seems related to #1 |
Ok, I see what you mean, I will take a look and see if there is a better way to do this then that works with Linux as I've not come across this issues with any other plugins. |
@cognitom - The only way I can see to get this to work not using the stdin is to write the contents of the file (file.contents) to a temporary on disk file and then pass that temporary file to phantomjs as phantomjs appears to insist on it being in a file. Maybe I'm wrong as I basically no experience of writing Gulp plugins and not very much with nodejs dev. How does that sound to you? |
fyi, ran into this problem and the commit fixed it. Would be super if you could push a new npm =) |
@joetoth thanks for remind me. |
I only briefly looked at node.js (spent the weekend playing around). Here is another example that creates a child processs and passes the the file.path. |
@joetoth it may not work in this case. The command |
hi, the same problem when you try to execute in Windows. |
There is an issue on Linux where the /dev/stdin is not readable and PhantomJS then returns the response:
Can't open '/dev/stdin'
To fix this you need to pass PhantomJS to the filename instead of the stdin and this change does just that. I've tested this on Mac OS X and Linux and it worked fine.