-
Notifications
You must be signed in to change notification settings - Fork 140
Error: Cannot read property 'type' of null #702
Comments
Definitely a bug in |
Interesting, I can reproduce your error in Atom, but it doesn't show anything on the CLI. Looking into this more. |
Nevermind, had copied a I used the following files to reproduce this: linter-eslint_GH702.zip Running Do you want to file a bug over there referencing this? |
These are the versions I was using
linter-eslint is at 7.3.1 |
Minimal test case: linter-eslint_GH702.zip Turns out just this is enough to trigger it: 'use strict';
const foo = (
<div style></div>
); |
I assume this is related to |
Oh, those are all just related to the Your comment did remind me to minimize the rule set as well, turns out it's just the |
Filed the above bug, marking this as closed since the bug isn't related to |
Looks like the next release of |
Getting following notification while typing:
![sep -14-2016 10-18-03 pm](https://cloud.githubusercontent.com/assets/5080854/18528439/5fd30dfc-7ac9-11e6-897c-f8f6567a474c.gif)
Thats the full message:
Not sure if it is an issue for this or
eslint-plugin-react
.Appreciate your work and support! 🙌
The text was updated successfully, but these errors were encountered: