jsdom browser never finishes to loading
willgm opened this issue · comments
It never finishes to load the jsdom browser, and keep like that forever:
~/proj/angular-jwt [jsdom ~1 *] » npm t
> angular-jwt@0.0.0 test /home/*****/proj/angular-jwt
> ng test
18 01 2017 14:48:01.583:WARN [karma]: No captured browser, open http://localhost:9876/
18 01 2017 14:48:01.627:WARN [karma]: Port 9876 in use
18 01 2017 14:48:01.637:INFO [karma]: Karma v1.2.0 server started at http://localhost:9877/
18 01 2017 14:48:01.638:INFO [launcher]: Launching browser jsdom with unlimited concurrency
18 01 2017 14:48:01.698:INFO [launcher]: Starting browser jsdom
18 01 2017 14:48:02.711:INFO [Node.js (linux; U; rv:v7.4.0) AppleWebKit/537.36 (KHTML, like Gecko)]: Connected on socket /#C5ASSEmEfLVpx_SKAAAA with id 34531896
You can se my try here:
https://github.com/willgm/angular2-jwt-poc/tree/jsdom
I'm using linux Fedora 25, node v7.4.0.
I've got the same problem. Running a basic test setup with jsdom launcher, it gets started, connected, but after 10sec karma tells, that the browser has stopped, because of missing feedback.
Windows 7, node v7.4.0
Just found this issue in the jsdom repository, looks like an error with jsdom in node v7.4.0
Downgrading to node v6.9.4 should fix the problem, I havn't tested this yet.
It seems like this is an issue with Node & Jsdom. As of 2017-01-31, node-7.5.0 has been released, which corrects the issue. It bothers me however that nothing was outputted. I will look a bit further into that specifically. The original issue though is fixed and thus I am closing the issue.