Closed Box-Of-Hats closed 4 years ago
Source of the issue found. I was using optional chaining in the source but VSCode was unhappy about it.
I've since removed the offending line and released 1.1.3
.
I will be investigating VSCode integration testing and improving the build steps to stop this from happening again
The extension is currently failing to activate when using version 1.1.2.
Temporary fix: Install version
1.1.1
instead