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

Document how to set this up alongside your regular jest config #22

Closed
Haroenv opened this issue Dec 21, 2017 · 6 comments
Closed

Document how to set this up alongside your regular jest config #22

Haroenv opened this issue Dec 21, 2017 · 6 comments

Comments

@Haroenv
Copy link

Haroenv commented Dec 21, 2017

  1. make two jest configs
  • one with your regular configuration
  • another one with eslint configuration
  1. add projects: ['path/to/jest-main.config.js', 'path/to/jest-eslint.config.js'] in the regular config file for Jest

Is that the recommended way?

@rogeliog
Copy link
Member

Hi! Thanks for reporting and sorry for the late response, I've been sick

Yeah, that is a great point! I love this, PR is more than welcome 😄

@Haroenv
Copy link
Author

Haroenv commented Dec 26, 2017

So projects is the way to go? I’ll make a PR to the readme when I have access to a computer if nobody else has done it before me

@ljharb
Copy link
Collaborator

ljharb commented Dec 26, 2017

The "projects" array is an array of paths, according to the docs: https://facebook.github.io/jest/docs/en/configuration.html#projects-array-string - not an array of configs.

As far as I'm aware, the only solution here is "two separate jest config files".

@azz
Copy link
Contributor

azz commented Dec 28, 2017

There's a PR to allow config objects here: jestjs/jest#5176

@keplersj
Copy link

@hph discusses this here: keplersj/jest-runner-prettier#7 (comment)

@macklinu
Copy link
Contributor

I will open a PR today to address this.

macklinu added a commit to macklinu/jest-runner-eslint that referenced this issue Feb 16, 2018
macklinu added a commit to macklinu/jest-runner-eslint that referenced this issue Feb 16, 2018
rogeliog pushed a commit that referenced this issue Feb 20, 2018
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

6 participants