Releases: microsoft/nodejstools
9-17-2015 Dev Build
See source code history for full information about recent fixes.
Highlights include:
- Fixes for inconsistent debugger behavior (#362, #246)
- We're changing up the IntelliSense experience, and would love to hear your feedback! Check out Options > Node.js > IntelliSense to customize any of this behavior.
This release is based on 43eae98. It has been signed and virus scanned, but has not been extensively tested and is not recommended for production environments.
Please report any bugs that you find in this build, and include the filename of the installer you used in your report.
You can also build NTVS from the latest sources.
NTVS 1.1 RC2.1
This is a minor update that contains fixes for several issues identified in the RC2 release. Specifically:
- #63 "intellisense disappears after closing VS when there is an incomplete statement in editor"
- #133 "Adding new Node.js project from existing code removes all other projects from solution"
- #316 "AnalysisIgnoredDirectories not working for sub-directories that have their own node_modules"
- #388 "NTVS 1.1 folder naming doesn't work with web publish"
- #398 "npm refresh hangs on refresh"
- #419 "Cannot start the node interactive window in VS 2013"
The links in the RC2 release below have been updated to point to the new installers. Please continue to install from the RC2 release links.
NTVS 1.1 RC2
We are pleased to announce the release of Node.js Tools 1.1 RC2 for Visual Studio.
Downloads
1. Download Visual Studio Community 2015
2. Download Node.js Tools 1.1 RC2
Looking for Visual Studio 2012 and 2013 support?
RELEASE NOTES
Node.js Tools for Visual Studio (NTVS) is a free, open-source plug-in that turns Visual Studio into a Node.js Integrated Development Environment (IDE). It supports a broad range of features including editing, IntelliSense, cross platform and remote debugging, edit and continue, npm integration, profiling, TypeScript, and an integrated REPL window. NTVS also includes a set of project templates that make it easy to quickly create and deploy websites to Microsoft Azure Websites or Cloud Services.
NTVS 1.1 RC2 is available for:
- Visual Studio Community 2015
- Visual Studio Community 2013
- Visual Studio 2015 Express for Web
- Visual Studio 2013 Express for Web (requires Update 2 or later)
- Visual Studio 2015 Professional or above
- Visual Studio 2013 Professional or above (requires Update 2 or later)
- Visual Studio 2012 Professional or above (requires Update 4)
Note that NTVS is not available for Visual Studio Express for Windows (or Windows Desktop)
Changes since 1.1 RC
ES6 IntelliSense Preview (new analysis engine)
You’ve been asking for ES6 support in Node.js tools for Visual Studio and we’re excited to give you a sneak peek in NTVS 1.1 RC2! Check out the new ES6 IntelliSense Preview mode available in Tools > Options > Node.js IntelliSense. This option will enable an experimental JavaScript editing experience, powered by TypeScript.
Head on over to our docs to learn more about this feature and some of it's limitations. We're constantly working to improve the IntelliSense experience, so please let us know what you think.
npm v3 Support
Look familiar? We thought it might... Luckily npm v3 is just around the corner, and one of the features we're most excited about is that dependencies are installed maximally flat, so you're less likely to run into MAX_PATH issues. NTVS 1.1 RC2 brings full support for this latest version in both solution explorer and the analysis engine.
Ready to give npm v3 beta a spin? Either follow the manual upgrade steps, or take advantage of the npm-windows-upgrade package from our friends at Microsoft DX.
Code Snippets
You've asked, and we listened! Thanks to our awesome intern, @avitalb, we finally have code snippet support in NTVS.
Simply press Ctrl+K +X to browse and select a snippet to insert, or type in the snippet name and press tab to complete it. Alternatively, highlight some existing code and press Ctrl+K+S to surround with. And of course, you can always modify or add your own snippets through the Snippet manager.
Write a great code snippet that you'd like to share? Let us know - we may be able to include it in the next update of NTVS.
Performance Improvements
Slow project load times are a drag, but not anymore. We have significantly improved our performance during project load when the dependency tree is large. In some cases we have seen over 80% gain in load times of large projects.
Debugging
We recently fixed an issue during debug-attach that was causing flakey debugging experiences for some users. So if breakpoints weren't working properly sometimes, or your app was having trouble running under the debugger, or things were generally inconsistent then hopefully this'll help 😃. Still running into issues with the latest release? Please let us know by filing an issue, and we'll try to get to it by 1.1 RTM.
Telemetry
We ❤️ Node.js, and strive to make NTVS to be the best Node.js development experience out there. So thank you so much to everyone who's already been active in the community here on GitHub. To help us further understand our user base, we will be collecting unidentifiable usage data to learn how we can make the experience even better.
We are extremely careful about instrumenting the code for telemetry for the following reasons.
- User Privacy - You can learn more about our privacy policy here.
- Performance - We ensure that the telemetry instrumentation does not negatively impact the performance of this product.
We have only added a couple of instrumentation points in this release, and we will be as transparent as possible with any future telemetry points we add to improve our learning on the usage of NTVS. And as always, please let us know if you have any questions or concerns.
Live Diagnostics Pane
There are some issues we just can't reproduce, so in order to help us track them down, we've added a new optional Live Diagnostics Pane, which you can enable by going to Tools > Node.js Tools > Diagnostic Info..., and check the Enable Node.js Tools Live Diagnostics output pane box. Then, during your debug sessions, output will be available in the Node.js Tools Live Diagnostics output pane
See #246 (comment) for more information, and thanks in advance for helping us track down these issues!
Numerous bug fixes
All across the product numerous issues have been fixed. We expect the RC release to provide both a much better user experience and improved stability. We would like to thank all of the people who took their time to report issues, send feedback for this release. We very much appreciate your help!
Known Issues
- #359 - Cloud deployment fails in certain scenarios. This issue will be fixed by in the next release, but in the meantime, you can work around the issue by unchecking the Show labels denoting browser and Node.js code in Solution Explorer option in Tools > Options > Node.js Tools
- ReSharper is known to cause code-completion, memory, and performance issues when enabled alongside NTVS. We recommend disabling at least ReSharper's JavaScript functionality if you are having problems.
- NTVS does not fully support build and test features of Visual Studio Online, but we are working to improve the experience. If you are having trouble, please file an issue so we can get to the bottom of it.
- We are constantly working to improve our code-completion and formatting to support the wide variety of modules and code styles. Please file an issue if you are running into unexpected behavior.
For a full list of issues, head on over to our issue tracker
Help make NTVS Better
NTVS is an open source project and we’re always willing to take high quality contributions. If you’d like to contribute, please check out our issue tracker for outstanding bugs and features which can be implemented. You can also help make NTVS better by reporting issues or helping out your fellow users on GitHub.
Miscellaneous thoughts on the release? Give us a shout-out on twitter!
8-4-2015 Dev Build
See source code history for information about recent fixes.
This release is based on 4f187a3. It has been signed and virus scanned, but has not been extensively tested and is not recommended for production environments.
Please report any bugs that you find in this build, and include the filename of the installer you used in your report.
You can also build NTVS from the latest sources.
NTVS 1.1 RC
We are pleased to announce the release of Node.js Tools 1.1 RC for Visual Studio.
Downloads
1. Download Visual Studio Community 2015
2. Download Node.js Tools 1.1 RC
Looking for Visual Studio 2012 and 2013 support?
RELEASE NOTES
Node.js Tools for Visual Studio (NTVS) is a free, open-source plug-in that turns Visual Studio into a Node.js Integrated Development Environment (IDE). It supports a broad range of features including editing, IntelliSense, cross platform and remote debugging, edit and continue, npm integration, profiling, TypeScript, and an integrated REPL window. NTVS also includes a set of project templates that make it easy to quickly create and deploy websites to Microsoft Azure Websites or Cloud Services.
NTVS 1.1 RC is available for:
- Visual Studio Community 2015
- Visual Studio Community 2013
- Visual Studio 2013 Express for Web (requires Update 2 or later)
- Visual Studio 2015 Professional or above
- Visual Studio 2013 Professional or above (requires Update 2 or later)
- Visual Studio 2012 Professional or above (requires Update 4)
Note that NTVS is not available for Visual Studio Express for Windows (or Windows Desktop)
Changes since 1.1 Beta
IntelliSense
Significantly improved performance
We've improved overall code analysis performance in this release by adding a new limit in place based on the depth of the npm tree so we don't have to analyze the world.
Additionally, we've added a new Quick IntelliSense mode available in Options > Node.js IntelliSense to limit it even further if you're still running into issues.
We're constantly working to improve the IntelliSense experience, so please let us know what you think of these improvements (especially if you notice a dip in quality of completions.)
Browser-mode for working with the DOM
There are tons of full-stack Node devs out there who are living in both browser-land and Node-land, and we've had many questions how to enable IntelliSense for the DOM... On the one hand we want to reduce clutter in the completions list, but on the other hand we want to provide as flexible an experience as possible. There was always a way to enable proper editing of DOM code within NTVS, but hats off to anyone who managed to discover it on their own.
In an effort to make this feature more discoverable and easier to use, we've introduced an explicit node/browser label on folders containing javascript files. Additionally, you can right click on any directory, and select Set as Content (browser code) or Set as Compile (Node.js code) to toggle between modes.
And of course, if you want to turn the labels off once you've configured your project, there's a new option to do so in:
Options > Node.js Tools > Show labels denoting browser and Node.js code in Solution Explorer
Debugger improvements
We fixed a race condition that was preventing many folks from launching the debugger in all sorts of unexpected ways. So if breakpoints weren't working properly sometimes, or your app was having trouble running under the debugger, or things were generally inconsistent then hopefully this'll help 😃.
Additionally we've fixed a source mapping bug that should make it a little easier to debug your TypeScript code if the output is being mapped to a single file.
Unit test running and debugging
We now adhere to a default 2 second timeout when running mocha unit tests, so your test runs should complete more quickly.
Additionally, we've added the ability to configure mocha by adding a config file to the project located at $(ProjectDirectory)\test\mocha.json. Adding the mocha.json file will result in the mocha tests running with the options specified. An example of a valid mocha.json file is:
{
"ui": "tdd",
"timeout": 300000,
"reporter": "xunit"
}And lastly, we've fixed some issues where tests with certain names weren't properly discovered/run, added better error logging so you can more easily track down issues in the future, and fixed that pesky bug preventing unit test debugging in VS 2015.
npm Integration
In this release, we've introduced an "Open Documentation" command on npm packages that lets you quickly hop to the documentation. It's the little things 😃.
New Dockerfile template
Docker is all the rage now, so to make it just a little easier to get started... we've added a new Linux-based dockerfile template (based on node:latest). Simply right click your project, select "Add New Item", and select the Dockerfile template to generate a Dockerfile for your project based on your current project settings.
Numerous bug fixes
All across the product numerous issues have been fixed. We expect the RC release to provide both a much better user experience and improved stability. We would like to thank all of the people who took their time to report issues, send feedback for this release. We very much appreciate your help!
Known Issues
- [VS2013 only] Be sure to customize the .gitignore file that Visual Studio places into your solution when you enable git source control, otherwise you may face issues with commits or continuous deployment.
- ReSharper is known to cause code-completion, memory, and performance issues when enabled alongside NTVS. We recommend disabling at least ReSharper's JavaScript functionality if you are having problems.
- NTVS does not fully support build and test features of Visual Studio Online, but we are working to improve the experience. If you are having trouble, please file an issue so we can get to the bottom of it.
- We are constantly working to improve our code-completion and formatting to support the wide variety of modules and code styles. Please file an issue if you are running into unexpected behavior.
For a full list of issues, head on over to our issue tracker
Thank You for Your Contributions
We expect the release of NTVS 1.1 RC to provide both a much better user experience and improved stability. Thanks so much to everyone who took their time to report issues and send feedback for this release. We very much appreciate your help!
We would also like to send special thanks to @kant2002, @jaredpar, and @lukedgr for contributing to this release through pull requests.
Help make NTVS Better
NTVS is an open source project and we’re always willing to take high quality contributions. If you’d like to contribute, please check out our issue tracker for outstanding bugs and features which can be implemented. You can also help make NTVS better by reporting issues or helping out your fellow users on GitHub.
Miscellaneous thoughts on the release? Give us a shout-out on twitter!
7-15-2015 Dev Build
Note: The VS 2015 build requires Visual Studio 2015 RC
See source code history for information about recent fixes.
This release is based on a4cd399. It has been signed and virus scanned, but has not been extensively tested and is not recommended for production environments.
Please report any bugs that you find in this build, and include the filename of the installer you used in your report.
You can also build NTVS from the latest sources.
6-15-2015 Dev Build
Note: The VS 2015 build requires Visual Studio 2015 RC
See source code history for information about recent fixes.
This release is based on a35e215. It has been signed and virus scanned, but has not been extensively tested and is not recommended for production environments.
Please report any bugs that you find in this build, and include the filename of the installer you used in your report.
You can also build NTVS from the latest sources.
5-13-2015 Dev Build
Note: The VS 2015 build requires Visual Studio 2015 RC
See source code history for information about recent fixes.
This release is based on 44bd6d6. It has been signed and virus scanned, but has not been extensively tested and is not recommended for production environments.
Please report any bugs that you find in this build, and include the filename of the installer you used in your report.
You can also build NTVS from the latest sources.