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
unable to test (win 10) #198
Comments
Update: Tried this on Windows 7 and got same result as expected. |
To fix this, I removed the package.json:
I'm not sure what the purpose is of At any rate, in Windows this is the reason for the errors: |
I should also mention that there was a resulting "TypeError: callback is not a function" from |
Fixed |
Why is this closed? The bug is still present! W10
|
@OscarKlintrot: Probably because it's a duplicate of open issue #201. |
@brandon-arnold: No, they are only related (as the author writes). I don't get the error in #201, only this one. Looks more like the author was satisfied with the help he got rather than that the bug got fixed. |
I guess |
I'm also getting this error and I'm on the very latest version of node (7.1.0), so I don't see that this has been fixed. I've applied the suggested changes and that does resolve the issue, but these seem like pretty fundamentally important command line arguments to me. This bug should be re-opened. |
@ozkey: Can you reopen this issue? |
I am also experiencing this issue. This works in windows 7. But it runs tests serially instead in parallel.
If I run the tests without the "--serial" option they will hang indefinitely at the end. What concerns me are also the warning messages.
|
Created a fresh new app and was unable to run "npm test" (Windows 10)
it looks like it tries to run a linux script in (\node_modules.bin\acorn)
the error:
The text was updated successfully, but these errors were encountered: