-
-
Notifications
You must be signed in to change notification settings - Fork 75
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
'loc' of null error when using babel-eslint as a custom parser #21
Comments
@mysticatea Could you try changing
and rerun the linter please? |
Sure, but I got the same result. Could you run |
Thank you. But sorry, I didn't find meaningful different.... (I checked I realized your screenshot has |
Maybe I got it. |
I've got the same bug here (my configuration seems to be the same as @Robula) |
Yes. This happens when a code is using stage 0-3 syntaxes or type annotations. I'm working on this, but I need more time. The cause is that |
Thank you for the explanation and your efforts to resolve this @mysticatea. |
Thank you for your patience. I'm still working in progress, but I have gotten that eslint/eslint#8755 is accepted at the last ESLint TSC Meeting and can advance babel/babel-eslint#542 to remove the monkey patching. |
|
eslint
Version: 4.10.0vue-eslint-parser
Version: 2.0.1-beta.2babel-eslint
Version: 8.0.2This is directly related to the issue I created here vuejs/eslint-plugin-vue#189.
I have discovered that the above issue is not resident in
eslint-plugin-vue
and that the issue likely lies with the interactions betweenbabel-eslint
andvue-eslint-parser
.As described in vuejs/eslint-plugin-vue#189 the combination of
vue-eslint-parser
andbabel-eslint
produces a error when running the linter.Example
The text was updated successfully, but these errors were encountered: