-
-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
watch:test doesn't work #424
Comments
Update - this is what I get in about 10 sec: <--- Last few GCs ---> 96789 ms: Mark-sweep 1378.6 (1456.9) -> 1378.5 (1456.9) MB, 935.2 / 0 ms [allocation failure] [GC in old space requested]. <--- JS stacktrace ---> ==== JS stack trace ========================================= Security context: 00000027931E3AD1 FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory npm ERR! Windows_NT 10.0.10586 npm ERR! Please include the following file with any support request: npm ERR! Windows_NT 10.0.10586 |
ok, I used latest packages and it seems like it all works now!
|
might be related to your use of "awesome-typescript-loader": "^0.16.0-rc.0" I suspect the problem is with typescript perhaps related to microsoft/TypeScript#7444, how I wish that typescript could just do type warnings and strip them.leaving compilation to Babel.. |
No, that actually didn't help. Still having this problem. Overall, it's like a lottery now... :( |
I use 'npm run watch:test' and when it initially starts all tests run. When I change the file with a test and save it, nothing happens. So it doesn't react on code changes. It used to work before.
The text was updated successfully, but these errors were encountered: