Fixed behavior in browser when used with mocha.js version 1.9.0 #136
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
|
Ugh, mocha defines a global process function. Bummer. Thanks for the PR, I'll take a look later today. |
briancavalier
added a commit
that referenced
this pull request
Apr 5, 2013
Fixed behavior in browser when used with mocha.js version 1.9.0
Author
|
Thank you for the quick response! |
Member
|
Seems like a safer check, anyways. :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a problem with defining nextTick function when you use when.js in browser together with Mocha.js 1.9.0
I've just added additional check for existence of method nextTick in process object.
If doesn't change any logic, but fixes the problem.