It turns out #1262 introduced a bug in sourcemaps, which caused the VSCode plugin to crash because of negative column numbers. 😦 The key fix in this PR is removing the + here:
Fixing this restores correct behavior. This is fairly urgent because the VSCode plugin is currently broken if the user installs the latest Civet.
I also added a feature to the LSP / VSCode plugin: if there are nonfatal errors (via Error nodes), so there's still a transpiled document, we still get TypeScript diagnostics. Example:
It turns out #1262 introduced a bug in sourcemaps, which caused the VSCode plugin to crash because of negative column numbers. 😦 The key fix in this PR is removing the
+here:Fixing this restores correct behavior. This is fairly urgent because the VSCode plugin is currently broken if the user installs the latest Civet.
I also added a feature to the LSP / VSCode plugin: if there are nonfatal errors (via
Errornodes), so there's still a transpiled document, we still get TypeScript diagnostics. Example: