Skip to content

io.js and ES6 support

Jump to bottom
Paul van Brenk edited this page Dec 12, 2017 · 4 revisions

🎵Note: This documentation is outdated at this point, especially when using the Node tools in Visual Studio 2017. We're working on update docs, and will redirect you to those when they're ready.

Configuring your project to use io.js

You can configure NTVS to use io.js instead of Node.js by right-clicking your project, and selecting Properties. From there you can change your node.exe path to point to io.js instead. image

ES6 Support in the Editor

We are working on it, but we currently support only a subset of ES6 features. This page will be updated soon with more complete documentation, but here are some of the highlights until then:

  • We support let statements (in 'use strict mode')
  • We support ES6 generator functions.
  • We also support (const x = 42;)

ES6 Usage in the Editor

Some ES6 usage will cause IntelliSense to fail in a broader sense - this includes things that involve new syntax. For example arrow functions will give syntax errors, but new methods on array just won’t show up in IntelliSense and won’t be analyzed. New scoping rules would probably just give wonky IntelliSense. So really only things that involve new syntax would show up as being broken (display errors and otherwise hurt IntelliSense).

Until we implement those features, you can work around any IntelliSense issues by ignoring directories for analysis

Clone this wiki locally