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

Jest is not recognized as an internal or external command #92

Open
prikx opened this issue May 7, 2020 · 4 comments
Open

Jest is not recognized as an internal or external command #92

prikx opened this issue May 7, 2020 · 4 comments

Comments

@prikx
Copy link

prikx commented May 7, 2020

I just started the javascript track finished and submitted Hello World, but when I was to test the two-fer code and entered "npm test" I got this error:

[email protected] test C:\Users\patrick\Exercism\javascript\two-fer
jest --no-cache ./*

'jest' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! Test failed. See above for more details.

Troubleshooting Information

Version

Current: 3.0.13
Latest: 3.0.13

Operating System

OS: windows
Architecture: amd64

Configuration

Home: C:\Users\Patrick
Workspace: C:\Users\Patrick\Exercism
Config: C:\Users\Patrick\AppData\Roaming\exercism
API key: d8ae*****************************57f

API Reachability

GitHub:
* https://api.github.com
* [connected]
* 247.9201ms

Exercism:
* https://api.exercism.io/v1/ping
* [connected]
* 348.8878ms

@NobbZ
Copy link
Member

NobbZ commented May 8, 2020

Have you run npm install in the two-fer folder?

cc @exercism/javascript

@NobbZ NobbZ transferred this issue from exercism/cli May 8, 2020
@github-actions
Copy link

github-actions bot commented May 8, 2020

This repository is restricted to Exercism's core team. Please open issues in exercism/exercism/issues.

@github-actions github-actions bot closed this as completed May 8, 2020
@NobbZ NobbZ reopened this May 8, 2020
@prajwalpoojary
Copy link

I'm having the same issue. Does anyone have a workaround for this problem?

@SleeplessByte
Copy link
Member

This usually happens when npm install hasn't ran. Have you've ran npm install? You'll need to do this for each exercise you work on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants