I have been working a lot with Power Shell ISE and debugging scripts, PS ISE is good but not the best as a debugger. I was attending a Microsoft event when I was introduced to my new favorite editor, Visual Studio Code editor, which was released to public preview on April 14, 2016. You can customize it by installing extensions to add new languages, themes, debuggers, and to connect to additional services. Unlike PS ISE, the extensions run in a separate process. One of the features I like is the side-by-side code editing.
Some of the improvements as of May:
- Editor: Ability to trim automatically inserted whitespace, a new key binding to select all find matches, and the Peek view is now resizable.
- Linting: ESLint now supports the ability to fix all problems and TSLint supports quick fixes and file exclusion.
- Languages: Code completion (IntelliSense), Go To and Peek Definition, and Find All Occurrences support for CSS variables in CSS, SCSS, and LESS files.
- Workbench: A new integrated Terminal allows you to stay in VS Code while using your platform’s shell, we’ve added the ability to remove key bindings, and we’ve made progress on Tab support, which you can preview using the Insiders Release.
- Debugging: You can now control how the Debug Console is revealed and we’ve improved stepping performance for Node.js applications with large numbers of local variables.
- Extensions: You can now list, install, and uninstall extensions from the command line. For extension authors, we’ve expanded our debug, TextMate grammar, and command APIs and we’ve improved the Language Server Protocol.
Here is a link to the Visual Studio Code site with a good overview and a download link.