Visual Studio Code has built-in support for editing style sheets in CSS
.scss and Less
.less. This support includes:
We have support for selectors, properties and values. Use
kb(editor.action.triggerSuggest) to get a list of context specific options.
kb(editor.emmet.action.expandAbbreviation) to expand the current abbreviation. John deere fs19.
Tip: See the CSS section of the Emmet cheat sheet for valid abbreviations.
We also support User Defined Snippets.
Syntax coloring & Color preview
As you type we provide syntax highlighting as well as in context preview of colors.
Syntax Verification & Linting
We support CSS version <= 2.1, Scss version <= 3.2 and Less version <= 1.7.
Goto symbol in file
Hovering over a selector or property will provide an HTML snippet that is matched by the CSS rule.
Goto Declaration and Find References
This is supported for keyframes and variables in the same file.
Note: Cross file references ('imports') are not resolved.
Transpiling Sass and Less into CSS
VS Code can integrate with Sass and Less transpilers through our integrated task runner. We can use this to transpile
.less files into
.css files. Let's walk through transpiling a simple Sass/Less file.
Step 1: Install a Sass or Less transpiler
For this walkthrough, let's use either the node-sass or less Node.js module.
Step 2: Create a simple Sass or Less file
Open VS Code on an empty folder and create a
styles.less file. Place the following code in that file:
For the Less version of the above file, just change
Visual Studio Code Css Intellisense
Note: This is a very simple example, which is why the code is almost identical between both file types. In more advanced scenarios, the syntaxes and constructs will be much different.
Step 3: Create tasks.json
The next step is to set up the task configuration. To do this open the Command Palette with
kb(workbench.action.showCommands) and type in
Configure Task Runner, press
kbstyle(Enter) to select it.
This will create a sample
tasks.json file in the
.vscode folder. The initial file has a large number of examples within it.
Tip: While the sample is there to help with common configuration settings, IntelliSense is available for the
tasks.json file as well to help you along. Use
kb(editor.action.triggerSuggest) to see the available settings.
The first example shows how to use configure tasks for TypeScript compilation. We will simply modify that configuration for transpiling Less/Sass instead:
Under the covers we interpret
lessc as an external task runner exposing exactly one task: the transpiling of Sass/Less files into CSS files. The command we run is
node-sass styles.scss > styles.css or
lessc styles.less > styles.css.
Step 4: Run the Build Task
As this is the only task in the file you can execute it by simply pressing
kb(workbench.action.tasks.build) (Run Build Task). At this point you will see an additional file show up in the file list
The sample Sass/Less file did not have any compile problems, so by running the task all that happened was a corresponding
styles.css file was created.
Automating Sass/Less compilation
Let's take things a little further and automate Sass/Less compilation with VS Code. We can do so with the same task runner integration as before, but with a few modifications.
Step 1: Install Gulp and some plug-ins
We will use Gulp to create a task that will automate Sass/Less compilation. We will also use the gulp-sass plug-in to make things a little easier. The Less plug-in is gulp-less.
Note: gulp-sass and gulp-less are Gulp plug-ins for the
lessc modules we were using before. There are many other Gulp Markdown plug-ins you can use, as well as plug-ins for Grunt.
Step 2: Create a simple Gulp task
Open VS Code on the same folder from before (contains
tasks.json under the
.vscode folder), and create
gulpfile.js at the root. Place the following code in that file:
What is happening here?1. We are watching for changes to any Sass/Less file at the root of our workspace, i.e. the current folder open in VS Code.2. We take the set of Sass/Less files that have changed, and run them through our respective compiler, i.e.
gulp-less.3. We now have a set of CSS files, each named respectively after their original Sass/Less file. We then put these files in the same directory.
Step 3: Modify the configuration in tasks.json for watching
To complete the tasks integration with VS Code, we will need to modify the task configuration from before, to set a watch on the default Gulp task we just created. Your tasks configuration should now look like this:
Step 4: Run the Build Task
Again, as this is the only task in the file you can execute it by simply pressing
kb(workbench.action.tasks.build) (Run Build Task). But this time, we've set a watch so the status bar should indicate that on the left-hand side.
At this point, if you create and/or modify other Less/Sass files, you will see the respective CSS files generated and/or changes reflected on save. You can also enable
Auto Save to make things even more streamlined.
If you want to stop the watch, you can press
kb(workbench.action.tasks.build) again and click
Terminate Running Task in the message box. Or you can use the Command Palette with
kb(workbench.action.showCommands) and find the terminate command there.
Customizing CSS, Sass and Less Settings
You can configure the following lint warnings as User or Workspace Settings.
Tip: Head over to this topic to get an overview of User and Workspace Settings.
To configure an option for CSS, use
css.lint. as the prefix to the id; for Sass and Less, use
Set a setting to
error if you want to enable lint checking, use
ignore to disable it. Lint checks are performed as you type.
|compatibleVendorPrefixes||When using a property with a vendor-specific prefix (for example ||ignore|
|vendorPrefix||When using a property with a vendor-specific prefix for example ||warning|
|duplicateProperties||Warn about duplicate properties in the same ruleset||ignore|
|emptyRules||Warn about empty rulesets||warning|
|importStatement||Warn about using an ||ignore|
|boxModel||Do not use ||ignore|
|universalSelector||Warn when using the universal selector ||ignore|
|zeroUnits||Warn when having zero with a unit e.g. ||ignore|
|fontFaceProperties||Warn when using ||warning|
|hexColorLength||Warn when using hex numbers that don't consist of three or six hex numbers||error|
|argumentsInColorFunction||Warn when an invalid number of parameters in color functions e.g. ||error|
|unknownProperties||Warn when using an unknown property||warning|
|ieHack||Warn when using an IE hack ||ignore|
|unknownVendorSpecificProperties||Warn when using an unknown vendor-specific property||ignore|
|propertyIgnoredDueToDisplay||Warn when using a property that is ignored due to the display. For example with ||warning|
|important||Warn when using ||ignore|
|float||Warn when using ||ignore|
|idSelector||Warn when using selectors for an id ||ignore|
Read on to find out about:
- Configure Tasks - Dig into Tasks to help you transpile your Sass and Less to CSS.
- Editing Evolved - Find out about the rich set of features the editor offers for languages such as CSS.
- HTML - CSS is just the start, HTML is also very well supported in VS Code.
Q: Do you provide a color selector?
A: No, this is currently not supported.
Q: Do you support the indentation based Sass syntax (.sass) ?
A: No, this is currently not supported.
How To Use Visual Studio Code
In this module you will:
Visual Studio Code Install
- Create the files for a website
Prettify Css Visual Studio Code
- Familiarity with one or more programming languages and a markup language such as HTML
- A computer that's running one of the following:
- Windows: Windows 7, 8, 10
- Mac: macOS 10.9 or later
- Linux: Ubuntu, Debian, Red Hat, Fedora, or SUSE