v2023.5.0
Wednesday, May 03, 2023
This release focused on include Justin Grote's new "attach .NET debugger" debug
configuration for binary PowerShell modules, and on handling start-up failures more
gracefully. If the start-up fails because the configured PowerShell is out-of-date,
instead of a confusing "undefined" error message we now detect the problem, inform the
user with a pop-up message of it, and offer to open the installation and/or update
instructions.
vscode-powershell
- #️⃣ 🙏 vscode-powershell #4549 - Update readme and troubleshooting docs.
- ✨ 🙏 vscode-powershell #4548 - Use named debug configurations instead of duplicating them.
- 🐛 🚨 vscode-powershell #4547 - Fix flaky test.
- 🐛 🛫 vscode-powershell #4543 - Update startup logic to handle session failure reasons.
- #️⃣ 🙏 vscode-powershell #4534 - Add ESBuild Problem Matcher Extension. (Thanks @JustinGrote!)
- 🐛 🙏 vscode-powershell #4521 - Handle end-of-support PowerShell with error message.
- ✨ 👷 vscode-powershell #4518 - Enable Mocha Test Explorer Integration. (Thanks @JustinGrote!)
- 🐛 🔍 vscode-powershell #4517 - Fix
attachDotnetDebuggerwith custom config. (Thanks @fflaten!) - 🐛 🔍 vscode-powershell #4516 - Add new debug configurations to
package.json. (Thanks @JustinGrote!) - #️⃣ 🔍 vscode-powershell #4511 - Add additional debug configuration templates for Pester and binary modules. (Thanks @JustinGrote!)
- #️⃣ 🔍🙏 vscode-powershell #4510 - Improve extension authoring experience with new Build Tasks and Launch Configs. (Thanks @JustinGrote!)
- ✨ 👷 vscode-powershell #4502 - Enable VS Code unit tests in Linux CI.
- ✨ 🙏 vscode-powershell #4498 - Enable ESLint
explicit-function-return-type. - ✨ 🔍 vscode-powershell #3903 - Add
attachDotnetDebuggerdebug option. (Thanks @JustinGrote!)
PowerShellEditorServices v3.8.4
- 🐛 🛫 vscode-powershell #4509 - Set session failure with reason when applicable.
- ✨ 📖 PowerShellEditorServices #2016 - Add guide to configure Neovim. (Thanks @csc027!)