Skip to content
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

Error when running tests #10

Closed
bnjmnt4n opened this issue Jan 10, 2017 · 2 comments
Closed

Error when running tests #10

bnjmnt4n opened this issue Jan 10, 2017 · 2 comments
Labels
locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting.

Comments

@bnjmnt4n
Copy link
Contributor

I'm running Node 6.2.1 on Windows 10. When running npm test on a fresh repo, I get the following error:

$ npm test

> prettier@0.0.2 test C:\Users\weeseng\Documents\GitHub\prettier
> jest

TypeError: string.replace is not a function
    at string (C:\Users\weeseng\Documents\GitHub\prettier\node_modules\jest-util\build\index.js:45:19)
    at p (C:\Users\weeseng\Documents\GitHub\prettier\node_modules\jest\node_modules\jest-cli\build\SearchSource.js:65:26)
    at new SearchSource (C:\Users\weeseng\Documents\GitHub\prettier\node_modules\jest\node_modules\jest-cli\build\SearchSource.js:101:34)
    at Runtime.createHasteContext.then.hasteMap (C:\Users\weeseng\Documents\GitHub\prettier\node_modules\jest\node_modules\jest-cli\build\jest.js:191:20)
    at process._tickCallback (internal/process/next_tick.js:103:7)
npm ERR! Test failed.  See above for more details.

Not too familiar with Jest, so I can't really help debug :(

@jlongster
Copy link
Member

jlongster commented Jan 10, 2017

Hm, thanks for the report! I will look into it later today. I just cloned a fresh repo and it worked locally on OSX on node v6.9.1.

@bnjmnt4n
Copy link
Contributor Author

I've tried it out, and have a fix locally. Will send a PR soon!

@lock lock bot added the locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting. label Jul 8, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Jul 8, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked-due-to-inactivity Please open a new issue and fill out the template instead of commenting.
Projects
None yet
Development

No branches or pull requests

2 participants