This repository has been archived by the owner on Sep 28, 2020. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 121
Problems with ESLint 2.10.1 and babel-eslint #92
Comments
gkubisa
added a commit
to gkubisa/elm-app-boilerplate
that referenced
this issue
May 15, 2016
`npm run test:js` fails with ESLint errors when "eslint v2.10.1" is installed, while "eslint v2.9.0" works fine. Probably the same issue as reported here: webpack-contrib/eslint-loader#92
Waiting for eslint/eslint#6182 to be fixed. |
As a temporary solution you can set parser in query in webpack.config.js preLoaders: [
{
test: /\.js$/,
loader: 'eslint?parser=babel-eslint',
exclude: /node_modules/,
}
], |
I'm getting an error which looks like:
Not sure if it's the same problem. |
@sebinsua You could try against eslint/eslint#6183 . There's a proposed fix. |
Closing given the combination works again. 👍 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
There's something going on with ESLint 2.10.1, eslint-loader, and babel-eslint combination. They had an issue in 2.10.0 that broken eslint-loader and babel-eslint. It was fixed in 2.10.1. It still fails with eslint-loader, though.
I set up an example illustrating this. If you execute
npm run test:lint
, the linting process completes successfully. If you runnpm start
, you'll start seeing errors like this:It's not picking up the parser for some reason. I did try setting
at my
common
configuration to make sure it really points to the configuration but this didn't have any effect.It's possible this is ESLint core issue and that their fix missed some corner case breaking ESLint. I am opening the issue here to see if other users are seeing similar behavior with this particular combination.
The text was updated successfully, but these errors were encountered: