Issue with karma-runner and the has-binary dep
See original GitHub issueAlso filed in the karma-runner repo: https://github.com/karma-runner/karma/issues/1534
I have some jasmine tests where the describe block is named toJSON
. Somehow we get to this line of code in the has-binary
module that this project depends on:
if (obj.toJSON) {
obj = obj.toJSON();
}
toJSON
isn’t a function so this just blows up.
Also, by the way, seems like that code is included twice in the socket.io.js
bundle.
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
"npm install karma" fails on windows · Issue #1609 - GitHub
I have the latest version of node installed: C:\>npm -v 2.14.4 C:\>node -v v4.1.2 I try installing karma via the docs and I...
Read more >Issue with Karma runner executing test cases - Stack Overflow
The problem is when I try to execute test cases it isn't executing any tests rather it just stuck at a point. When...
Read more >Karma - Spectacular Test Runner for Javascript
The main goal for Karma is to bring a productive testing environment to developers. The environment being one where they don't have to...
Read more >third party component notices - Grammarly
The below listed Third Party Components may be contained in the Software, Services, or Site. These Third-Party Component notices are ...
Read more >Karma Runner - Stryker Mutator
Bring your own test runner ... Note: karma v2.0.3 has a known issue which makes it impossible to use it with Stryker. please...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
yes i believe this is fixed
@kentor @wesleycho was this fixed by
1.7.2
?