Closed jayshah123 closed 5 years ago
This is caused by the fact that the plugin uses a JS construct which is not supported yet by electron node. You can use the setting eslint.runtime
to point to a never version of node that supports that feature.
eslint.runtime
is an Unknown configuration setting in VSCode settings.
eslint.nodePath
was a valid configuration setting but issue still persists after updating eslint.nodePath
to point to node v10.6.0
@dbaeumer
Finally, I just downloaded vscode 1.35.1
and it uses eslint extension version 1.9.0
where issue no longer occurs.
Vscode version:
1.25.1
Eslint plugin version:1.4.12
Node version:v8.11.3
Mac Os: High Sierra I tried to update Eslint plugin version to1.9.0
but even after install it remains1.4.12
. I tried to update VSCode itself, but it says no updates available.In package.json
Eslint terminal output window: