The Visual Studio Code 0.10.10 release features a fiesta of language improvements, including...
The JSDoc comment format is now understood and used to improve IntelliSense proposals and parameter hints:
You now get IntelliSense proposals for properties in 'ECMAScript 3 style classes':
IntelliSense offers both inferred proposals and the global identifiers of the project. The inferred symbols are presented first, followed by the global identifiers (with the document icon), as you can see in the image above.
commonjs support has been improved as well:
There is now support for JSX/React:
Tip: To get IntelliSense for React/JSX, install the typings for
tsd install react-globalor
typings install --ambient react-globalfrom the terminal.
Tip: When you use eslint for linting (see below) and you used
eslint --initto create an eslint configuration and you answered
yesto "Do you use React?", then the setting
experimentalObjectRestSpreadis enabled. Support for ObjectRestSpread is not yet provided by Salsa but it is on the roadmap (see #2103).
There is now support for React Native:
Tip: To get IntelliSense for React Native, install the typings for
tsd install react-nativeor
typings install --ambient react-nativefrom the terminal. Or even better... if you also want debugging support then install the preview of the React Native extension.
Tip: There is a known issue in that Salsa Doesn't Provide IntelliSense When Using Import Statements.
allowJs property to
true in the
tsccompiler does not detect the presence of a
jsconfig.jsonfile automatically. Use the
–pargument to make
tsc -p jsconfig.json.
Finally, the TypeScript compiler
The following sections describe a few of VS Code's features that have changed with the move to Salsa and provide information about maintaining previous behaviors.
Here are the steps to set up
npm install eslintto install
eslintinto your workspace or
npm install -g eslintto install it globally.
- install the VS Code eslint extension.
eslint --initto create an initial eslint configuration by answering questions or by picking a popular configuration.
Tip: If you use JSON as the format of the eslint configuration file, then VS Code can provide you with IntelliSense when you edit the
temp. This implicit behavior has changed in favor of an explicit list defined by the user. Therefore if you use...
webpackthen exclude the output folder, e.g.,
Tip: After editing the
If you do not have a
jsconfig.json in your workspace then the following defaults are used:
excludelist includes the
node_modulesfolder and the folder defined by the
What has not changed, but that you should be aware of, is that if you have no
js-is-jsx etension deprecation
js-is-jsx extension is no longer needed since Salsa gives you coloring for JSX constructs inside
.js files out of the box. We recommend you uninstall this extension.
No longer supported
- The source language level is now always ECMAScript 6. Previously, there was support to define a lower level using the
jsconfig.json. This support has been removed and the
targetattribute is now only used by
AMDmodules. This hasn't worked in all cases and support for
AMDto resolve references across files is currently no longer supported.
- There is no longer support for IntelliSense in
scriptsections inside HTML documents.
Languages - TypeScript
VS Code now ships with the latest TypeScript 1.8.2 version.
Languages - C#
C# language support is now an optional install from the Marketplace. You can install it from within VS Code by searching for 'C#':
Or if you already have a project with C# files, VS Code will prompt you to install the extension as soon as you open a C# file.
Check out all the new features and update to Visual Studio Code v0.10.10:
You're looking visual and studious,
- Ninja Ed