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

Setting up in a nested directory #322

Closed
skippednote opened this issue May 10, 2018 · 3 comments
Closed

Setting up in a nested directory #322

skippednote opened this issue May 10, 2018 · 3 comments

Comments

@skippednote
Copy link

Environment

  1. node -v: [8.11.1]
  2. npm -v: [5.6]
  3. npm ls react-scripts (if you haven’t ejected): [1.1.4]
  4. Operating system: [Ubuntu 18.04]

Here is my project structure:

root
|- frontend
|- backend
|- .vscode

Can I configure the extension in some way that the jest runner can figure out where the npm scripts and binary is?
I'm using create-react-app
I tried settings up "jest.pathToJest": "frontend/node_modules/.bin/react-scripts test --env=jsdom" but it didn't help.

@skippednote
Copy link
Author

Resolved it.
Here is the final setting:

{
  "jest.pathToJest": "npm test:unit --",
  "jest.rootPath": "frontend"
}

@axhamre
Copy link

axhamre commented Nov 2, 2018

I'm on CRA 2.0 and I've done exactly like above - but unfortunately the extension does nothing for me 😕

Running the tests manually works well though.

@mzrt
Copy link

mzrt commented Sep 26, 2019

I'm on CRA 2.0 and I've done exactly like above - but unfortunately the extension does nothing for me 😕

Running the tests manually works well though.

I have the same problem.

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

No branches or pull requests

4 participants