Merge branch 'vnext' of https://github.com/microsoft/vscode-docs into vnext

release-notes/images/1_45/js-debug-copy.gif

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:5aac5e0ee723592023a444b52a1b18991e2dd8771f3f3ac3448db7b9a819b097
+size 261049

release-notes/images/1_45/js-debug-profiling.gif

@@ -0,0 +1,3 @@
+version https://git-lfs.github.com/spec/v1
+oid sha256:aa408e7457602fb5cd0eed53a654bba7b13f0377b9585fcdf55bde3f912b32b2
+size 2577177

release-notes/v1_45.md

@@ -206,6 +206,34 @@ Editor links in Markdown files and links in the Markdown preview can now point t
 
 Preview features are not ready for release but are functional enough to use. We welcome your early feedback while they are under development.
 
+### New JavaScript debugger
+
+This month we've continued making progress on our new JavaScript debugger. It's installed by default on Insiders, and can be installed [from the Marketplace](https://marketplace.visualstudio.com/items?itemName=ms-vscode.js-debug-nightly) in VS Code Stable. You can start using it with your existing launch configurations by enabling the `debug.javascript.usePreview` setting. Here are some new features added this month:
+
+**Profiling Support**
+
+You can capture CPU profiles from your Node.js or browser applications by clicking the new "Profile" button in the Call Stack view, or using the **Debug: Take Performance Profile** command. Once you do, you can choose how long the profile will run: until you stop it, for a length of time, or until you hit another breakpoint.
+
+After the profile ends, it's saved in your workspace folder and visualized in VS Code. When you open the profile, code lenses are added to your files containing performance information at a function level and for certain 'hot' lines. Unlike profiles captured in many other tools, the recorded profile is sourcemap-aware.
+
+![Animation showing the process of taking a profile](images/1_45/js-debug-profiling.gif)
+
+*Theme: Earthsong, Font: Fira Code*
+
+**Auto-Attach Integration**
+
+When `debug.javascript.usePreview` is turned on, VS Code's [auto-attach](https://code.visualstudio.com/docs/nodejs/nodejs-debugging#_auto-attach-feature) will use a new method provided by `js-debug` that allows all terminals to work similarly to the Debug Terminal. Compared to auto-attach using the existing debugger:
+
+- The debugger is attached immediately allowing you to hit breakpoints early on in the program
+- Child processes are debugged automatically
+- There's no process-polling overhead during auto attach.
+
+**Copy Complex Values from Variables View**
+
+Previously, trying to copy complex values, like objects, from the vscode **Variables** view would often result in truncated or incomplete data. Changes in VS Code and js-debug allows us to copy the complete value.
+
+![Animation showing copying and pasting a very large array](images/1_45/js-debug-copy.gif)
+
 ### Workspace symbol search in all open TypeScript/JavaScript projects
 
 When using TypeScript 3.9+, VS Code's [workspace symbol search](https://code.visualstudio.com/docs/editor/editingevolved#_open-symbol-by-name) now includes results from all opened JavaScript and TypeScript projects by default. We previously only searched the project of the currently active file.