Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upTypeScript: TypeError: Cannot read property 'type' of null #956
Comments
Closed
This comment has been minimized.
This comment has been minimized.
rochapablo
commented
Oct 5, 2017
•
Running
|
This comment has been minimized.
This comment has been minimized.
adyshimony
commented
Jan 29, 2018
|
Check this out |
This comment has been minimized.
This comment has been minimized.
stale
bot
commented
May 10, 2018
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
stale
bot
added
the
stale
label
May 10, 2018
This comment has been minimized.
This comment has been minimized.
|
The workaround for this issue is:
Mentioned in this comment: eslint/typescript-eslint-parser#439 (comment) |
feross
closed this
May 11, 2018
lock
bot
locked as resolved and limited conversation to collaborators
Aug 9, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
lautarodragan commentedJul 19, 2017
•
edited
I'm getting this error when running standard on a typescript project:
Versions of stuff I'm using:
Followed the instructions on the README. Installed
eslint-plugin-typescriptandtypescript-eslint-parserglobally.Also tried installing standard as a devDependency.
package.jsonlooks like this:Tried running
npm run standardto use the standard installed on the project instead of the global one, but came to the same result.Also tried running against *.tsx files (it's a typescript + reactjs project), got the same result.
If I run it with no arguments, it matches against
webpack.config.jsanddevServer.jsonly, and seems to be working well in that case (reported a bunch of style errors and offered to auto --fix them).Am I doing anything wrong?