TypeError: Cannot read property 'type' of undefined

[mcknasty]

What version of this package are you using?

xxxxx@xxxxx~/codez/c8$ grep 'standard": "' package.json
    "standard": "^16.0.4",
xxxxx@xxxxx:~/codez/c8$

The commit on C8 I am testing against is 8e56b23d007c30432ca9956aaee91a00cb8dd4c0

What operating system, Node.js, and npm version?

xxxxx@xxxxx:~/codez/c8$ uname -r
5.15.79.1-microsoft-standard-WSL2
xxxxx@xxxxx:~/codez/c8$

Affected versions of node and npm

Node Version	NPM Version	Error Collected
v10.21.1	v7.24.2	TypeError: Cannot read property 'type' of undefined
v12.22.12	v8.19.3	TypeError: Cannot read property 'type' of undefined
v14.21.2	v9.5.0	TypeError: Cannot read property 'type' of undefined
v16.19.0	v9.5.0	TypeError: Cannot read property 'type' of undefined
v18.14.0	v9.5.0	TypeError: Cannot read property 'type' of undefined

What happened?

See errors above.

What did you expect to happen?

Expected linting to pass as it has in the past.

Are you willing to submit a pull request to fix this bug?

Possibly. I think the problem is downstream in eslint. Eslint just pushed a newer version a few days ago

[exactlyaron]

Had the same issue too.

Looks like it's because of this issue - estools/esquery#135

Which has been fixed here - estools/esquery#138

eslint probably needs to be updated to the new version of esquery

[exactlyaron]

@mcknasty - eslint have pinned the version of esquery to an older version that doesn't have the bug so standard should be fine now - it's fine for me on CI jobs were it was failing earlier on today.

[mcknasty]

Yes, this is looking fixed to me too. Thank you for linking the issues @exactlyaron.