You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.
When the extension is enabled, it very proactively tries to parse all the projects in the VSCode workspace. If the projects use a newer ECMAScript for JavaScript with for example import-commands, they are all marked as having syntax errors. After digging a bit I found that there is a configuration parameter that could be set as the server starts up (for example --js.ecmascript-version=2019) but I didn't find any way to set it. Did I miss something or is there another way to enable the compatibility?
The text was updated successfully, but these errors were encountered:
When the extension is enabled, it very proactively tries to parse all the projects in the VSCode workspace. If the projects use a newer ECMAScript for JavaScript with for example import-commands, they are all marked as having syntax errors. After digging a bit I found that there is a configuration parameter that could be set as the server starts up (for example --js.ecmascript-version=2019) but I didn't find any way to set it. Did I miss something or is there another way to enable the compatibility?
The text was updated successfully, but these errors were encountered: