Change:
this._compilerOptions = options || ts.getDefaultCompilerOptions(); this._compilerOptions.allowNonTsExtensions = true; // because of JS* and mirror model we need this this._compilerOptions.module = ts.ModuleKind.CommonJS; // because of JS* <ins> this._compilerOptions.target = options && options.target !== undefined ? options.target : ts.ScriptTarget.Latest; // because of JS* </ins> } getCompilationSettings(): ts.CompilerOptions {

Discussion:
Type: <bBug</bWhen working in a CSS document, if I use the query, a pop-up occurs stating: I have not noticed any negative impact besides the pop-up obscuring terminal menu. When looking at the output, the log states: VS Code version: Code 1.76.1 (, 2023-03-08T16:32:00.131Z) OS version: WindowsNT x64 10.0. Modes: Sandboxed: No <details<summarySystem Info</summary </details<details<summaryExtensions (11)</summaryExtensionVersion ------ better-comments3.0.2 prettier-vscode9.10.4 gml-support1.7.4 vscode-language-babel0.0.37 git-graph1.30.0 powershell2023.2.1 vsliveshare1.0.5834 vscode-css-variables-autocomplete0.3.1 LiveServer5.7.9 code-spell-checker2.19.0 vscode-icons12.2.0 </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
Type: Bug same probleme, working in a CSS document, using query, a pop-up occurs stating: VS Code Version: 1.76.1 (Universal) (, 2023-03-08T16:32:00.131Z) OS version: MacOs Monterey 12.6.3 (21G419) Electron: 19.1.11 Chromium: 102.0.5005.196 16.14.2 V8: 10.2.154.26-electron.0 OS: Darwin x64 21.6.0 Sandboxed: No
A similar error seem to be happening when writing in a .scss file. Writing or pasting makes the error popup appear, but a does not. To be a little clearer, here's a list of patterns with that can be pasted in a .scss file to trigger the error : - ( there's a space here at the end) - - (note: does not trigger the error.)

Type: Bug same problem here, working in a CSS document, using query, a pop-up and related terminal occurs stating: Error: selectionRange must be contained in fullRange at Function.validate (/Users/james/Desktop/Visual Studio ) at new t (/Users/james/Desktop/Visual Studio ) at V (/Users/james/Desktop/Visual Studio ) at c (/Users/james/Desktop/Visual Studio ) at (/Users/james/Desktop/Visual Studio ) at Object.asDocumentSymbols (/Users/james/Desktop/Visual Studio ) at i (/Users/james/Desktop/Visual Studio ) at n.provideDocumentSymbols (/Users/james/Desktop/Visual Studio ) <img width="1231" alt="스크린샷 2023-03-26 오전 10 32 42" src="https://user-"
Mismo problema, esperar alguna actualización para que lo corrijan? ! !
I'm having the same issue.
I'm confused. It says this was fixed but I'm still having the same issue. Nothing i've clicked on in this page is telling me how to fix it and use
I will be in the next insider build
Same issue
Same issue
As mentioned, the fix is in 1.78. If you still see this, please add the build you are on and a small code sample to reproduce.

Hey everyone, 2015 is almost over, but we still need an editor configuration file to edit what is currently "JavaScript as supported by browsers". I'd like to avoid . That would also solve issues like . I'll make a PR to pressure y'all even more :stuckouttonguewinking_eye:
:+1:
yes
:+1: :+1: :+1:
Closing for now:
We are save to make this change for Dec because going forward with project salsa the default will be the latest for JS files (#Microsoft/TypeScript/6017)