Skip to content
This repository was archived by the owner on Feb 26, 2024. It is now read-only.

Issues with running "npm test" on Windows 10 #331

Closed
jshin49 opened this issue May 8, 2016 · 4 comments
Closed

Issues with running "npm test" on Windows 10 #331

jshin49 opened this issue May 8, 2016 · 4 comments

Comments

@jshin49
Copy link

jshin49 commented May 8, 2016

Hi there I've been having issues with npm test, Karma unit tests, on the step-2.

Anyone knows why?

The following is the error-log:
INFO [karma]: Karma v0.12.37 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
INFO [Chrome 50.0.2661 (Windows 10 0.0.0)]: Connected on socket wGn9Y8QeTAPEkhAocJiU with id 80523642
ERROR [karma]: [TypeError: The header content contains invalid characters]
TypeError: The header content contains invalid characters
at ServerResponse.OutgoingMessage.setHeader (_http_outgoing.js:348:11)
at ServerResponse.res.setHeader (C:\Users\jshin\Dropbox\Dev\workspace\Angular\angular-phonecat\node_modules\connect\lib\patch.js:134:22)
at Object.setNoCacheHeaders (C:\Users\jshin\Dropbox\Dev\workspace\Angular\angular-phonecat\node_modules\karma\lib\middleware\common.js:76:12)
at C:\Users\jshin\Dropbox\Dev\workspace\Angular\angular-phonecat\node_modules\karma\lib\middleware\karma.js:109:18
at C:\Users\jshin\Dropbox\Dev\workspace\Angular\angular-phonecat\node_modules\karma\lib\middleware\common.js:63:35
at FSReqWrap.readFileAfterClose as oncomplete
npm ERR! Test failed. See above for more details.

@gkalpak
Copy link
Member

gkalpak commented May 9, 2016

This must be related to outdated dependencies. Try updating http-server (see #322 (comment)).
There is already a PR for updating all dependencies (and the tutorial itself).

@jshin49
Copy link
Author

jshin49 commented May 9, 2016

I have already done updating http-server to the newest version.

Maybe I should try to update all of the outdated dependencies?

@gkalpak
Copy link
Member

gkalpak commented May 10, 2016

You might also try updating karma. I think that one was causing that error (possibly because of using http-server under the hood). BTW, you can take a look at the pending PR: #326

@jshin49
Copy link
Author

jshin49 commented May 10, 2016

Following the PR: #326 resolved my issue. All I did is updating the package.json and run npm install

@jshin49 jshin49 closed this as completed May 10, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants