-
Notifications
You must be signed in to change notification settings - Fork 2k
not compatible with node v0.6 #159
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
Comments
We've got a branch under development working on full 0.6 compatibility - there are still a few bugs in the meantime. For now, you can either |
that helps, thx |
@AvianFlu: Would these issues be related to how, under 0.6.2, I've never seen and 'end' or 'close' event from the proxy? |
@AvianFlu: Never mind. That seems to be an oddity related to Chromium. I get 'end' events when I use Lynx. Weird. Worrisome? |
Can you please publish the 0.7.7 changes to npm :D? |
Any update on when 0.6 support is going to land? |
Next week. There will be significant refactoring over this coming weekend, with 0.6 support at the top of the priority list. |
Just checking in if there's been progress on 0.6 compat, I'd love to help test it out with the locker project, just let me know if it's ready for that :) |
Thanks for your patience and support! |
Hi, I just tried "npm install http-proxy", but I still have the same error : npm ERR! Error: No compatible version found: http-proxy Can you please help me? |
Looks like you're still on node 0.6.1, they set the minimum at 0.6.6. |
The minimum version is node 0.6.6 because of bugs that were fixed in core - you'll need to update. |
This is what I get when I try to install it via npm
The text was updated successfully, but these errors were encountered: