Change:
})); this.toDispose.push(this.editor.onKeyDown((e: IKeyboardEvent) => this.onKeyDown(e))); this.toDispose.push(this.editor.onDidChangeModelContent(() => { <del> this.wordToLineNumbersMap = null; </del> <ins> this.updateInlineValueDecorationsScheduler.schedule(); </ins> })); this.toDispose.push(this.editor.onDidChangeModel(() => { <del> const sf = this.debugService.getViewModel().focusedStackFrame; </del> <ins> const stackFrame = this.debugService.getViewModel().focusedStackFrame; </ins> const model = this.editor.getModel(); <del> this.editor.updateOptions({ hover: !sf || !model || model.uri.toString() !== sf.source.uri.toString() }); </del> <ins> this.editor.updateOptions({ hover: !stackFrame || !model || model.uri.toString() !== stackFrame.source.uri.toString() }); </ins> this.closeBreakpointWidget(); this.toggleExceptionWidget(); this.hideHoverWidget(); this.updateConfigurationWidgetVisibility(); <del> this.wordToLineNumbersMap = null; this.updateInlineDecorations(sf); </del> <ins> this.updateInlineValueDecorationsScheduler.schedule(); </ins> })); this.toDispose.push(this.editor.onDidScrollChange(() => this.hideHoverWidget)); this.toDispose.push(this.debugService.onDidChangeState((state: State) => {

Discussion:
Right now we expose an API to cells, and to webviews, but we don't publish types for this. The webview API is very simple, but the renderer will be somewhat more complex. We should consider either publishing these in or in a separate package.
This would be helpful for I think a or something would be a good place for it. Aside, it'd be cool if ts s could be contributed to... Right now we'd need a whole separate NPM scope to have separate I believe.
We can just PR a package called The naming of packages is only constrained by the maintainers' policy, and there are types that don't correspond to single packages, e.g.
Poor wording, I mean the project would need a different and for the client code vs the extension host code. (Or just know not call acquireApi outside of the client context of course. )
Oh, yea. In the sample renderer/code generator I'm using project references to keep things separated -- that also lets us use only in the renderer and output es6 modules (only) for webpack.
PR submitted

Bug Set "debug.inlineValues": true. Set breakpoint somewhere. After paused on the step, goto the end of the line and hit enter. Before After VS Code version: Code 1.20.0 (, 2018-02-07T17:02:34.244Z) OS version: Darwin x64 16.7.0 <details<summarySystem Info</summary </details<details<summaryExtensions (9)</summaryExtensionVersion ------ EditorConfig0.12.0 vscode-eslint1.4.5 vscode-great-icons2.1.24 auto-rename-tag0.0.15 code-beautifier1.7.2 vscode-scss0.6.2 mssql1.3.0 cpptools0.14.6 licenser1.1.1 (1 theme extensions excluded) </detailsReproduces only with extensions
I acknowledge the bug. This is just how decoartions are behaving, unfortunetly the inline decorations do not seem to have an option to not grow beyond the line. maybe you have an idea how to solve this? fyi in case you are interested into looking for a fix
debugger.inlineValues uses the editor's decorator api. A fix we can do is that if the editor is edited , then we re-sync the inlineValue decorators I'm not sure how this works but would love it if the bug was assigned to me so I can see it in my issues list
that's a good idea. can you please add to our project so we can assign some issues to him?