jiebi/CodeConvo huggingface dataset:
Change:
Issue Type: <bBug</bOpen a Webview (for example: Help -Release Note) and start the search (Ctrl+F) and write the search term (for example: "Update") Only "u" (first letter) is selected on the view and not the current tipped search term. ! Notice: If i pressed "enter" then the full term is selected on the view. This behavier was other in the previous version (1.52.1) VS Code version: Code 1.54.3 (, 2021-03-15T10:55:45.459Z) OS version: WindowsNT x64 10.0. <details<summarySystem Info</summary </details<details<summaryExtensions (31)</summaryExtensionVersion ------ mock-debug0.45.4 cortex-vsc2.1.0 npm-intellisense1.3.1 vscode-markdownlint0.40.1 jshint0.11.0 vscode-eslint2.1.19 vscode-npm-script0.3.18 vscode-firefox-debug2.9.2 auto-close-tag0.5.10 code-runner0.11.3 vscode-test-explorer2.19.6 code-coverage1.2.3 vscode-docker1.11.0 csharp1.23.9 python2021.3. vscode-pylance2021.3.3 jupyter2021.3. cpptools1.2.2 powershell2021.2.2 debugger-for-chrome4.12.12 vetur0.33.1 java0.76.0 vscode-xml0.15.0 vscode-yaml0.17.0 markdown-preview-enhanced0.5.17 vscodeintellicode1.2.12 vscode-java-debug0.32.1 vscode-java-dependency0.18.2 vscode-java-pack0.13.0 vscode-java-test0.28.1 vscode-maven0.28.0 </details<!-- generated by issue reporter --
(Experimental duplicate detection) Thanks for submitting this issue. Please also check if it is already covered by an existing one, like: <!-- score: 0.526 --<!-- potentialduplicatescomment --
The search behaviour changed between Electron 9.3.5 and Electron 11.4.1. The parameter should now be whenever we're doing a search for the first time.

Discussion:
// FindNext must be false for a first request const findOptions: FindInPageOptions = { forward: options.forward, <del> findNext: false, </del> <ins> findNext: true, </ins> matchCase: options.matchCase, medialCapitalAsWordStart: options.medialCapitalAsWordStart };

return; } <del> const options = { findNext: true, forward: !previous }; </del> <ins> const options = { findNext: false, forward: !previous }; </ins> if (!this._findStarted) { this.startFind(value, options); return;
Change:
From an HTML file, type that suggestions show up to expand , but when is typed, suggestions stop showing up. Potential code pointers: Try adding for relevant languages (everything other than css to stylus) here If that doesn't work, we might need to add to some regexes for
Can you add character to expand suggestions also? For example and to show suggestions list for . !
I don't think that's a common use case, considering works.
+ or + doesn't expand anything. I must write + + to expand this.
can you set to ?
It works perfect, thanks.
Sorry but I have noticed that in file inside tag with extenstion installed doesn't work. Is this from extension implementation or not ? !
please file that issue with Vetur

Discussion:
* Mapping between languages that support Emmet and completion trigger characters */ export const LANGUAGE_MODES: { [id: string]: string[] } = { <del> 'html': ['!', '.', '}', ':', '*', '$', ']', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'jade': ['!', '.', '}', ':', '*', '$', ']', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'slim': ['!', '.', '}', ':', '*', '$', ']', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'haml': ['!', '.', '}', ':', '*', '$', ']', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'xml': ['.', '}', '*', '$', ']', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'xsl': ['!', '.', '}', '*', '$', ']', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], </del> <ins> 'html': ['!', '.', '}', ':', '*', '$', ']', '/', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'jade': ['!', '.', '}', ':', '*', '$', ']', '/', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'slim': ['!', '.', '}', ':', '*', '$', ']', '/', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'haml': ['!', '.', '}', ':', '*', '$', ']', '/', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'xml': ['.', '}', '*', '$', ']', '/', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'xsl': ['!', '.', '}', '*', '$', '/', ']', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], </ins> 'css': [':', '!', '-', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'scss': [':', '!', '-', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'sass': [':', '!', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'less': [':', '!', '-', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'stylus': [':', '!', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], <del> 'javascriptreact': ['!', '.', '}', '*', '$', ']', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'typescriptreact': ['!', '.', '}', '*', '$', ']', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'] </del> <ins> 'javascriptreact': ['!', '.', '}', '*', '$', ']', '/', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'], 'typescriptreact': ['!', '.', '}', '*', '$', ']', '/', '0', '1', '2', '3', '4', '5', '6', '7', '8', '9'] </ins> }; export function isStyleSheet(syntax: string): boolean {
Change:
<!-- Do Not Delete This! featurerequesttemplate --Currently, if a notebook kernel outputs or some other mime type for which there is no registered renderer, a message is shown instead of the output. For mime types, the output should be rendered as plain text.
This is a really good idea.
After more than a year, I still think this is a very interesting idea that's worth a try. We might need to add match for mimetypes for the output renderer contribution. I assigned this to you for now.

Discussion:
} break; default: <ins> if (outputInfo.mime.indexOf('text/') > -1) { disposables.get(outputInfo.id)?.dispose(); const disposable = renderText(outputInfo, element, latestContext); disposables.set(outputInfo.id, disposable); } </ins> break; } if (element.querySelector('div')) {

return undefined; } <del> const pickedMimeTypeRenderer = mimeTypes[pick]; const innerContainer = this._generateInnerOutputContainer(previousSibling, pickedMimeTypeRenderer); </del> <ins> const selectedPresentation = mimeTypes[pick]; let renderer = this.notebookService.getRendererInfo(selectedPresentation.rendererId); if (!renderer && selectedPresentation.mimeType.indexOf('text/') > -1) { renderer = this.notebookService.getRendererInfo('vscode.builtin-renderer'); } const innerContainer = this._generateInnerOutputContainer(previousSibling, selectedPresentation); </ins> this._attachToolbar(innerContainer, notebookTextModel, this.notebookEditor.activeKernel, index, mimeTypes); this.renderedOutputContainer = DOM.append(innerContainer, DOM.$('.rendered-output')); <del> const renderer = this.notebookService.getRendererInfo(pickedMimeTypeRenderer.rendererId); </del> this.renderResult = renderer <del> ? { type: RenderOutputType.Extension, renderer, source: this.output, mimeType: pickedMimeTypeRenderer.mimeType } : this._renderMissingRenderer(this.output, pickedMimeTypeRenderer.mimeType); </del> <ins> ? { type: RenderOutputType.Extension, renderer, source: this.output, mimeType: selectedPresentation.mimeType } : this._renderMissingRenderer(this.output, selectedPresentation.mimeType); </ins> <del> this.output.pickedMimeType = pickedMimeTypeRenderer; </del> <ins> this.output.pickedMimeType = selectedPresentation; </ins> if (!this.renderResult) { this.viewCell.updateOutputHeight(index, 0, 'CellOutputElement#renderResultUndefined');
Change:
Proposal: Example use case: GitLens running a git command and when it fails, create a new terminal which includes the error message in the header and the failed command ready to be run manually. This is generally useful for other applications (eg. welcome to the blah debug terminal, this is how it works, ...) cc
<img width="725" alt="Screen Shot 2021-04-01 at 12 25 57 PM" src="https://user-"
This is in main, very little to do since was already an option internally. Will bring this to next API sync.
alternative names: message, placeholder, placeHolder
Will probably go with to match .
Proposed API TPI:
Code: Result: <img width="398" alt="Screen Shot 2021-05-04 at 6 36 08 AM" src="https://user-"

Discussion:
* as normal. */ hideFromUser?: boolean; <ins> /** * A message to write to the terminal on first launch, note that this is not sent to the * process but, rather written directly to the terminal. This supports escape sequences such * a setting text style. */ message?: string; </ins> } /**

//#endregion <del> //#region Terminal initial text https://github.com/microsoft/vscode/issues/120368 export interface TerminalOptions { /** * A message to write to the terminal on first launch, note that this is not sent to the * process but, rather written directly to the terminal. This supports escape sequences such * a setting text style. */ readonly message?: string; } //#endregion </del> //#region Terminal icon https://github.com/microsoft/vscode/issues/120538 export interface TerminalOptions {

if ('pty' in nameOrOptions) { return extHostTerminalService.createExtensionTerminal(nameOrOptions); } <del> if (nameOrOptions.message) { checkProposedApiEnabled(extension); } </del> if (nameOrOptions.icon) { checkProposedApiEnabled(extension); }
Change:
We should adopt An easy fix is to just fallback when this happens, we need to make sure we don't save suggested renderer type if the webgl renderer is good though.
Can you add verification steps?
To verify: Context loss is achieved at a diff't limit for each computer. Using VS code stable - create as many terminals as needed to trigger context loss. When you reach that state, you'll see ! Now in Insider's, create the same number of terminals. You shouldn't see any of those context loss images.
very nice, I like how the fallback magically works

Discussion:
this._instanceId = TerminalInstance._instanceIdCounter++; this.hasHadInput = false; this._titleReadyPromise = new Promise<string>(c => { this._titleReadyComplete = c; });

this._webglAddon = new Addon(); try { this._xterm.loadAddon(this._webglAddon); <ins> this._webglAddon.onContextLoss(() => { this._logService.info(`Webgl lost context, disposing of webgl renderer`); this._disposeOfWebglRenderer(); this._safeSetOption('rendererType', 'dom'); }); </ins> this._storageService.store(SUGGESTED_RENDERER_TYPE, 'auto', StorageScope.GLOBAL, StorageTarget.MACHINE); } catch (e) { this._logService.warn(`Webgl could not be loaded. Falling back to the canvas renderer type.`, e);
Change:
Issue Type: <bBug</bCompare the appearance of the step-in/over/out buttons on the main debug toolbar with the same buttons that appear in the call stack. ! The ones in the call stack are enabled even when execution hasn't been suspended. VS Code version: Code - Insiders 1.56.0-insider (, 2021-04-02T05:15:44.248Z) OS version: Windows_NT x64 10.0. <!-- generated by issue reporter --
/assign
Great catch, and thanks for the fix
/verified

Discussion:
} }); <del> function registerCallStackInlineMenuItem(id: string, title: string, icon: Icon, when: ContextKeyExpression, order: number): void { </del> <ins> function registerCallStackInlineMenuItem(id: string, title: string, icon: Icon, when: ContextKeyExpression, order: number, precondition?: ContextKeyExpression): void { </ins> MenuRegistry.appendMenuItem(MenuId.DebugCallStackContext, { group: 'inline', order, when, <del> command: { id, title, icon } </del> <ins> command: { id, title, icon, precondition } </ins> }); } const threadOrSessionWithOneThread = ContextKeyExpr.or(CONTEXT_CALLSTACK_ITEM_TYPE.isEqualTo('thread'), ContextKeyExpr.and(CONTEXT_CALLSTACK_ITEM_TYPE.isEqualTo('session'), CONTEXT_CALLSTACK_SESSION_HAS_ONE_THREAD))!; registerCallStackInlineMenuItem(PAUSE_ID, PAUSE_LABEL, icons.debugPause, ContextKeyExpr.and(threadOrSessionWithOneThread, CONTEXT_CALLSTACK_ITEM_STOPPED.toNegated())!, 10); registerCallStackInlineMenuItem(CONTINUE_ID, CONTINUE_LABEL, icons.debugContinue, ContextKeyExpr.and(threadOrSessionWithOneThread, CONTEXT_CALLSTACK_ITEM_STOPPED)!, 10); <del> registerCallStackInlineMenuItem(STEP_OVER_ID, STEP_OVER_LABEL, icons.debugStepOver, threadOrSessionWithOneThread, 20); registerCallStackInlineMenuItem(STEP_INTO_ID, STEP_INTO_LABEL, icons.debugStepInto, threadOrSessionWithOneThread, 30); registerCallStackInlineMenuItem(STEP_OUT_ID, STEP_OUT_LABEL, icons.debugStepOut, threadOrSessionWithOneThread, 40); </del> <ins> registerCallStackInlineMenuItem(STEP_OVER_ID, STEP_OVER_LABEL, icons.debugStepOver, threadOrSessionWithOneThread, 20, CONTEXT_CALLSTACK_ITEM_STOPPED); registerCallStackInlineMenuItem(STEP_INTO_ID, STEP_INTO_LABEL, icons.debugStepInto, threadOrSessionWithOneThread, 30, CONTEXT_CALLSTACK_ITEM_STOPPED); registerCallStackInlineMenuItem(STEP_OUT_ID, STEP_OUT_LABEL, icons.debugStepOut, threadOrSessionWithOneThread, 40, CONTEXT_CALLSTACK_ITEM_STOPPED); </ins> registerCallStackInlineMenuItem(RESTART_SESSION_ID, RESTART_LABEL, icons.debugRestart, CONTEXT_CALLSTACK_ITEM_TYPE.isEqualTo('session'), 50); registerCallStackInlineMenuItem(STOP_ID, STOP_LABEL, icons.debugStop, ContextKeyExpr.and(CONTEXT_CALLSTACK_SESSION_IS_ATTACH.toNegated(), CONTEXT_CALLSTACK_ITEM_TYPE.isEqualTo('session'))!, 60); registerCallStackInlineMenuItem(DISCONNECT_ID, DISCONNECT_LABEL, icons.debugDisconnect, ContextKeyExpr.and(CONTEXT_CALLSTACK_SESSION_IS_ATTACH, CONTEXT_CALLSTACK_ITEM_TYPE.isEqualTo('session'))!, 60);
Change:
Steps that should work but don't (these will be verification steps): PowerShell for macOS if you don't have it what path was to () it as your default shell: VS Code from the dock/finder a workspace with the below task the task Actual Expected Something like: This is because we fail to get the UnixShellEnvironment. You can confirm this by looking in output, you should see:
another great verification step is replacing the command in the task and putting something like or . This will likely fail saying it couldn't find the command ... because the environment wasn't set up properly.
I'm still getting the actual output instead of the expected output when I repeated the verification steps on my Mac.

Discussion:
const systemShellUnix = await getSystemShell(OS, env); logService.trace('getUnixShellEnvironment#shell', systemShellUnix); <del> let command = `'${process.execPath}' -p '"${mark}" + JSON.stringify(process.env) + "${mark}"'`; let shellArgs = ['-ilc']; </del> // handle popular non-POSIX shells const name = path.basename(systemShellUnix); <ins> let command: string, shellArgs: Array<string>; </ins> if (/^pwsh(-preview)?$/.test(name)) { <del> command = `& ${command}`; </del> <ins> // Older versions of PowerShell removes double quotes sometimes so we use "double single quotes" which is how // you escape single quotes inside of a single quoted string. command = `& '${process.execPath}' -p '''${mark}'' + JSON.stringify(process.env) + ''${mark}'''`; </ins> shellArgs = ['-Login', '-Command']; <ins> } else { command = `'${process.execPath}' -p '"${mark}" + JSON.stringify(process.env) + "${mark}"'`; shellArgs = ['-ilc']; </ins> } logService.trace('getUnixShellEnvironment#spawn', JSON.stringify(shellArgs), command);
Change:
<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --The inlines values colors are currently hardcoded: These should be abstracted to a themable color, either its own dedicated color or one of the , I would recommend hint or info.
I agree with this. Let's put a help wanted, sounds like a good thing to be tackled by the community. If nobody is interested I can also look into this in the future
Thanks to this is now fixed can you maybe try this out with VS Code insiders from tomorrow and let us know how it works for you. The new color names are:
Thank you, will test. Cc EDIT: Doesn't appear to have landed in yesterdays insiders, will check tomorrow.

Discussion:
import { IUriIdentityService } from 'vs/workbench/services/uriIdentity/common/uriIdentity'; import { IContextKey, IContextKeyService } from 'vs/platform/contextkey/common/contextkey'; import { Expression } from 'vs/workbench/contrib/debug/common/debugModel'; <ins> import { themeColorFromId } from 'vs/platform/theme/common/themeService'; import { registerColor } from 'vs/platform/theme/common/colorRegistry'; </ins> const LAUNCH_JSON_REGEX = /.vscode/launch.json$/; const INLINE_VALUE_DECORATION_KEY = 'inlinevaluedecoration';

const MAX_INLINE_DECORATOR_LENGTH = 150; // Max string length of each inline decorator when debugging. If exceeded ... is added const MAX_TOKENIZATION_LINE_LEN = 500; // If line is too long, then inline values for the line are skipped <ins> export const debugInlineForeground = registerColor('editor.inlineValuesForeground', { dark: '#ffffff80', light: '#00000080', hc: '#ffffff80' }, nls.localize('editor.inlineValuesForeground', "Color for the debug inline value text.")); export const debugInlineBackground = registerColor('editor.inlineValuesBackground', { dark: '#ffc80033', light: '#ffc80033', hc: '#ffc80033' }, nls.localize('editor.inlineValuesBackground', "Color for the debug inline value background.")); </ins> class InlineSegment { constructor(public column: number, public text: string) { }

renderOptions: { after: { contentText, <del> backgroundColor: 'rgba(255, 200, 0, 0.2)', margin: '10px' }, dark: { after: { color: 'rgba(255, 255, 255, 0.5)', } }, light: { after: { color: 'rgba(0, 0, 0, 0.5)', } </del> <ins> backgroundColor: themeColorFromId(debugInlineBackground), margin: '10px', color: themeColorFromId(debugInlineForeground) </ins> } } };
Change:
This would be useful since we can now navigate the tabs via the keyboard, so you could hit <keybinding, up n times, enter to focus that terminal.
Also it's a little tough to tell which split pane is actually focused right now, perhaps some extra visual hint?
Opening to double check what the ideal keybinding would be on each platform
Let's go with ctrl/cmd+shift+ for this, to align with 's navigate tabs keybinding.

Discussion:
getFindState(): FindReplaceState; findNext(): void; findPrevious(): void; <ins> focusTabsView(): void; </ins> registerProcessSupport(isSupported: boolean): void; /**

registerAction2(class extends Action2 { constructor() { super({ <ins> id: TERMINAL_COMMAND_ID.FOCUS_TABS_VIEW, title: { value: localize('workbench.action.terminal.focus.tabsView', "Focus Terminal Tabs View"), original: 'Focus Terminal Tabs View' }, f1: true, category, keybinding: { primary: KeyMod.CtrlCmd | KeyMod.Alt | KeyCode.KEY_T, weight: KeybindingWeight.WorkbenchContrib, when: ContextKeyExpr.or(KEYBINDING_CONTEXT_TERMINAL_TABS_FOCUS, KEYBINDING_CONTEXT_TERMINAL_FOCUS), }, precondition: KEYBINDING_CONTEXT_TERMINAL_PROCESS_SUPPORTED, }); } async run(accessor: ServicesAccessor) { await accessor.get(ITerminalService).focusTabsView(); } }); registerAction2(class extends Action2 { constructor() { super({ </ins> id: TERMINAL_COMMAND_ID.FOCUS_NEXT, title: { value: localize('workbench.action.terminal.focusNext', "Focus Next Terminal"), original: 'Focus Next Terminal' }, f1: true,

} } <ins> public async focusTabsView(): Promise<void> { await this.showPanel(true); const pane = this._viewsService.getActiveViewWithId<TerminalViewPane>(TERMINAL_VIEW_ID); pane?.terminalTabbedView?.focusTabsView(); } </ins> private _getIndexFromId(terminalId: number): number { let terminalIndex = -1; this.terminalInstances.forEach((terminalInstance, i) => {

]; } <ins> public focusTabsView(): void { this._terminalTabsFocusContextKey.set(true); this._tabsWidget.domFocus(); } </ins> public focusFindWidget() { this._findWidgetVisible.set(true); const activeInstance = this._terminalService.getActiveInstance();

this._focus(); } <ins> public focusTabsView(): void { this._terminalTabbedView?.focusTabsView(); } </ins> private _focus() { this._terminalService.getActiveInstance()?.focusWhenReady(); }

SPLIT_IN_ACTIVE_WORKSPACE = 'workbench.action.terminal.splitInActiveWorkspace', RELAUNCH = 'workbench.action.terminal.relaunch', FOCUS_PREVIOUS_PANE = 'workbench.action.terminal.focusPreviousPane', <ins> FOCUS_TABS_VIEW = 'workbench.action.terminal.focusTabsView', </ins> FOCUS_NEXT_PANE = 'workbench.action.terminal.focusNextPane', RESIZE_PANE_LEFT = 'workbench.action.terminal.resizePaneLeft', RESIZE_PANE_RIGHT = 'workbench.action.terminal.resizePaneRight',
Change:
We currently still patch the shell environment into the shared process environment which can be very slow. We should try to remove this code:
Adding Daniel for making sure the terminal side of things is not badly impacted by such a change.

Discussion:
import { assertIsDefined } from 'vs/base/common/types'; import { Emitter, Event } from 'vs/base/common/event'; import { WindowError } from 'vs/platform/windows/electron-main/windows'; <del> import { resolveShellEnv } from 'vs/platform/environment/node/shellEnv'; </del> import { IProtocolMainService } from 'vs/platform/protocol/electron-main/protocol'; export class SharedProcess extends Disposable implements ISharedProcess {

// Always wait for first window asking for connection await this.firstWindowConnectionBarrier.wait(); <del> // Resolve shell environment this.userEnv = { ...this.userEnv, ...(await resolveShellEnv(this.logService, this.environmentMainService.args, process.env)) }; </del> // Create window for shared process this.createWindow();
Change:
<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --- Version: 1.56.0-insider (user setup) Commit: Date: 2021-04-27T06:15:26.914Z Electron: 12.0.4 Chrome: 89.0.4389.114 14.16.0 V8: 8.9.255.24-electron.0 OS: Windows_NT x64 10.0. Steps to Reproduce: Here is the error message ! The text version: <!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --
I'm seeing this too. I worked around it for now by creating with as the content. Interestingly, I still get schema completion in files so I guess this (built-in) extension is not even meant to be providing that? <details</details
I guess this was fixed by

Discussion:
"dependencies": { "jsonc-parser": "^3.0.0", "request-light": "^0.4.0", <del> "vscode-json-languageservice": "^4.1.2", </del> <ins> "vscode-json-languageservice": "^4.1.3", </ins> "vscode-languageserver": "^7.0.0", "vscode-uri": "^3.0.2" },

https-proxy-agent "^2.2.4" vscode-nls "^4.1.2" <del> vscode-json-languageservice@^4.1.2: version "4.1.2" resolved "https://registry.yarnpkg.com/vscode-json-languageservice/-/vscode-json-languageservice-4.1.2.tgz#c3873f791e23488a8b373e02c85c232bd625e27a" integrity sha512-atAz6m4UZCslB7yk03Qb3/MKn1E5l07063syAEUfKRcVKTVN3t1+/KDlGu1nVCRUFAgz5+18gKidQvO4PVPLdg== </del> <ins> vscode-json-languageservice@^4.1.3: version "4.1.3" resolved "https://registry.yarnpkg.com/vscode-json-languageservice/-/vscode-json-languageservice-4.1.3.tgz#851564e529e649c13b844f10a80ea1d9095591a9" integrity sha512-m/wUEt4zgCNUcvGmPr1ELo+ROQNKBgASpdOOAEpcSMwYE/6GzULZ1KfBhbX9or7qnC4E0oX+wwW+lrN3EUWCgw== </ins> dependencies: jsonc-parser "^3.0.0" minimatch "^3.0.4"