jest-community / jest-runner-eslint

An ESLint runner for Jest
MIT License
480 stars 46 forks source link

jest-runner-eslint disagreeing with command line eslint and editor #69

Open samselikoff opened 5 years ago

samselikoff commented 5 years ago

I'm trying to get jest-runner-eslint setup but its results are disagreeing with the results from running eslint from the command line (as well as my editor).

It does seem like both jest and eslint (and editor) are using .eslintrc.js, because if I change them both runners are affected. But I can't get the two to agree on certain files.

For example I have a file response.js, and my editor shows these errors:

image

image

When I run eslint lib/response.js I get

image

But when I run jest, I get

image


Here's my configs:

// jest.config.js
let eslint = {
  displayName: "lint",
  runner: "jest-runner-eslint",
  testMatch: ["<rootDir>/lib/response.js"]
};

module.exports = {
  projects: [eslint]
};
// .eslintrc.js
module.exports = {
  root: true,
  parser: "babel-eslint",
  plugins: ["jest"],
  extends: [
    "eslint:recommended",
    "plugin:jest/recommended",
    "plugin:jest/style"
  ],
  env: {
    "jest/globals": true,
    es6: true
  },
  rules: {
    camelcase: 0,
    "object-curly-spacing": 0,
    quotes: 0,
    "array-bracket-spacing": 0,
    "no-var": 0,
    "object-shorthand": 0,
    "arrow-parens": 0,
    "no-unused-vars": ["error", { args: "none" }]
  },
  overrides: [
    {
      files: ["jest.config.js", "babel.config.js"],
      env: {
        browser: false,
        node: true
      }
    },
    {
      files: ["__tests__/**"],
      env: {
        browser: true
      }
    }
  ]
};
SimenB commented 5 years ago

Could you put together a reproduction we could pull down and see the error? We just use eslint's programmatic api, so different results sounds weird

samselikoff commented 5 years ago

Here ya go! https://github.com/samselikoff/jest-runner-eslint-issue-69

luizcieslak commented 5 years ago

@samselikoff did you manage to solve this? Got the same issue here

samselikoff commented 4 years ago

@luizcieslak haven't come back to it again so I don't think so.