-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Q stops working with Browserify >= 8.1.0 due to nextTick changes #1179
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
This was referenced Mar 24, 2015
slorber
referenced
this issue
in defunctzombie/node-process
Mar 24, 2015
This was referenced Mar 24, 2015
A PR is available here defunctzombie/node-process#37 |
@substack @defunctzombie this can now be solved by uprading "process" dependency to 0.11 right? |
@slorber It's not just flipping the version. A couple of tests fail for the reasons in browserify/insert-module-globals#42 (under process to ^0.10.0). I'll try to get to it tmw. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Q works fine with Browserify 8.0.3 but has serious problems since 8.1.0.
This is related to changes done in nextTick implementation of node-process: #1018
Related Q issue: kriskowal/q#669
I don't know who of Q or Browserify should fix this but this makes Q unreliable in production.
The text was updated successfully, but these errors were encountered: