How to start using SASS in Visual Studio Code
In this article I will explain how to set up the SASS web compiler with Visual Studio Code so that you can start writing SASS code for your projects.
What is the SASS?
SASS (Synthetically Awesome Style Sheets) is a scripting language that allows you to create CSS code faster and save time by reducing repetitive output. SASS allows you to parameterise repetitive inputs through variables, create functions and use nested syntax to iterate across elements.
Why do we need a SASS compiler?
The browser can not read SASS, it reads CSS. Therefore you will need a way to turn the SASS code into CSS code, a process known as transpiling.
Visual Studio Code SASS Compiler
The Sass Compiler Web Extension for Visual Studio Code is one of the best ways to have your SASS files transpiled into CSS.
To do so simply type in “Live Sass Compiler” into the extensions marketplace.
In the bottom right hand side you will see a cog if it is already installed or an install button if it isn’t. In this case simply click the button and the Live Sass Compiler will install.
After installation is complete, you should see a ‘Watch Sass’ button in the blue menu bar at the bottom of the screen, similar to the one below:
Once the compiler has started, simply create a new file with the same name as the file containing your .css code, but name it .scss instead. Once you have typed in some Sass code into the ‘scss’ file, hit save or CTRL + s and you should see a .css.map file along with a new .css file if you don’t already have one.
The map file simple shows which SASS file is being transpiled into a specific CSS file. You have to make sure to transpile your code by saving your work before you can view the updates in browser.
CSS, SCSS and Less
Visual Studio Code has built-in support for editing style sheets in CSS .css , SCSS .scss and Less .less . In addition, you can install an extension for greater functionality.
Tip: Click on an extension tile above to read the description and reviews to decide which extension is best for you. See more in the Marketplace.
IntelliSense
VS Code has support for selectors, properties and values. Use ⌃Space (Windows, Linux Ctrl+Space ) to get a list of context specific options.
Proposals contain extensive documentation, including a list of browsers that support the property. To see the full description text of the selected entry, use ⌃Space (Windows, Linux Ctrl+Space ) .
Syntax coloring & color preview
As you type, there is syntax highlighting as well as in context preview of colors.
Clicking on a color preview will launch the integrated color picker which supports configuration of hue, saturation and opacity.
Tip: You can trigger between different color modes by clicking on the color string at the top of the picker.
You can hide VS Code’s color previews by setting the following setting:
To just disable it for css, Less and SCSS, use
Folding
You can fold regions of source code using the folding icons on the gutter between line numbers and line start. Folding regions are available for all declarations (for example, rule declarations) and for multiline comments in the source code.
Additionally you can use the following region markers to define a folding region: /*#region*/ and /*#endregion*/ in CSS/SCSS/Less or // #region and // #endregion In SCSS/Less.
If you prefer to switch to indentation based folding for CSS, Less and SCSS, use:
Emmet snippets
Emmet abbreviation support is built into VS Code, suggestions are listed along with other suggestions and snippets in the editor auto-completion list.
Tip: See the CSS section of the Emmet cheat sheet for valid abbreviations.
Syntax Verification & Linting
There is support for CSS version <= 2.1, Sass version <= 3.2 and Less version <= 2.3.
Note: You can disable VS Code’s default CSS, Sass or Less validation by setting the corresponding .validate User or Workspace setting to false.
Go to Symbol in file
You can quickly navigate to the relevant CSS symbol in the current file by pressing ⇧⌘O (Windows, Linux Ctrl+Shift+O ) .
Hovers
Hovering over a selector or property will provide an HTML snippet that is matched by the CSS rule.
Go to Declaration and Find References
This is supported for Sass and Less variables in the same file. CSS variables per the draft standards proposal are also supported.
There is jump to definition for @import and url() links in CSS, SCSS and Less.
CSS custom data
You can extend VS Code’s CSS support through a declarative custom data format. By setting css.customData to a list of JSON files following the custom data format, you can enhance VS Code’s understanding of new CSS properties, at-directives, pseudo-classes and pesudo-elements. VS Code will then offer language support such as completion & hover information for the provided properties, at-directives, pseudo-classes and pesudo-elements.
You can read more about using custom data in the vscode-custom-data repository.
Formatting
The CSS Languages Features extension also provides a formatter. The formatter works with CSS, LESS and SCSS. It is implemented by the JS Beautify library and comes with the following settings:
- css.format.enable — Enable/disable default CSS formatter.
- css.format.newlineBetweenRules — Separate rulesets by a blank line.
- css.format.newlineBetweenSelectors — Separate selectors with a new line.
- css.format.spaceAroundSelectorSeparator — Ensure a space character around selector separators ‘>’, ‘+’, ‘
The same settings also exist for less and scss .
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 .scss or .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 sass or less Node.js module.
Note: If you don’t have Node.js and the npm package manager already installed, you’ll need to do so for this walkthrough. Install Node.js for your platform. The Node Package Manager (npm) is included in the Node.js distribution. You’ll need to open a new terminal (command prompt) for npm to be on your PATH.
Step 2: Create a simple Sass or Less file
Open VS Code on an empty folder and create a styles.scss or styles.less file. Place the following code in that file:
For the Less version of the above file, just change $padding to @padding .
Note: This is a very simple example, which is why the source 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, run Terminal > Configure Tasks and click Create tasks.json file from template. In the selection dialog that shows up, select Others.
This will create a sample tasks.json file in the workspace .vscode folder. The initial version of file has an example to run an arbitrary command. We will modify that configuration for transpiling Sass/Less instead:
Step 4: Run the Build Task
As this is the only command in the file, you can execute it by pressing ⇧⌘B (Windows, Linux Ctrl+Shift+B ) (Run Build Task). The sample Sass/Less file should not have any compile problems, so by running the task all that happens is a corresponding styles.css file is created.
Since in more complex environments there can be more than one build task we prompt you to pick the task to execute after pressing ⇧⌘B (Windows, Linux Ctrl+Shift+B ) (Run Build Task). In addition, we allow you to scan the output for compile problems (errors and warnings). Depending on the compiler, select an appropriate entry in the list to scan the tool output for errors and warnings. If you don’t want to scan the output, select Never scan the build output from the presented list.
At this point, you should see an additional file show up in the file list styles.css .
If you want to make the task the default build task to run execute Configure Default Build Task from the global Terminal menu and select the corresponding Sass or Less task from the presented list.
Note: If your build fails or you see an error message such as "An output directory must be specified when compiling a directory", be sure the filenames in your tasks.json match the filenames on disk. You can always test your build by running sass styles.scss styles.css from the command line.
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.
We need to install gulp both globally ( -g switch) and locally:
Note: gulp-sass and gulp-less are Gulp plug-ins for the sass and lessc modules we were using before. There are many other Gulp Sass and Less plug-ins you can use, as well as plug-ins for Grunt.
You can test that your gulp installation was successful by typing gulp -v in the terminal. You should see a version displayed for both the global (CLI) and local installations.
Step 2: Create a simple Gulp task
Open VS Code on the same folder from before (contains styles.scss / styles.less and tasks.json under the .vscode folder), and create gulpfile.js at the root.
Place the following code in the gulpfile.js file:
What is happening here?
- Our default gulp task first runs the sass or less task once when it starts up.
- It then watches for changes to any SCSS/Less file at the root of our workspace, for example the current folder open in VS Code.
- It takes the set of SCSS/Less files that have changed and runs them through our respective compiler, for example gulp-sass , gulp-less .
- We now have a set of CSS files, each named respectively after their original SCSS/Less file. We then put these files in the same directory.
Step 3: Run the gulp default task
To complete the tasks integration with VS Code, we will need to modify the task configuration from before to run the default Gulp task we just created. You can either delete the tasks.json file or empty it only keeping the "version": "2.0.0" property. Now execute Run Task from the global Terminal menu. Observe that you are presented with a picker listing the tasks defined in the gulp file. Select gulp: default to start the task. We allow you to scan the output for compile problems. Depending on the compiler, select an appropriate entry in the list to scan the tool output for errors and warnings. If you don’t want to scan the output, select Never scan the build output from the presented list. At this point, if you create and/or modify Less or SASS files, you 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 make the gulp: default task the default build task executed when pressing ⇧⌘B (Windows, Linux Ctrl+Shift+B ) run Configure Default Build Task from the global Terminal menu and select gulp: default from the presented list.
Step 4: Terminate the gulp default Task
The gulp: default task runs in the background and watches for file changes to Sass/Less files. If you want to stop the task, you can use the Terminate Task from the global Terminal menu.
Customizing CSS, SCSS and Less Settings
You can configure the following lint warnings as User and Workspace Settings.
The validate setting allows you turn off the built-in validation. You would do this if you rather use a different linter.
| Id | Description | Default |
|---|---|---|
| css.validate | Enables or disables all css validations | true |
| less.validate | Enables or disables all less validations | true |
| scss.validate | Enables or disables all scss validations | true |
To configure an option for CSS, use css.lint. as the prefix to the id; for SCSS and Less, use scss.lint. and less.lint. .
Set a setting to warning or error if you want to enable lint checking, use ignore to disable it. Lint checks are performed as you type.
| Id | Description | Default |
|---|---|---|
| validate | Enables or disables all validations | true |
| compatibleVendorPrefixes | When using a property with a vendor-specific prefix (for example -webkit-transition ), make sure to also include all other vendor-specific properties e.g. -moz-transition , -ms-transition and -o-transition | ignore |
| vendorPrefix | When using a property with a vendor-specific prefix for example -webkit-transition , make sure to also include the standard property if it exists e.g. transition | warning |
| duplicateProperties | Warn about duplicate properties in the same ruleset | ignore |
| emptyRules | Warn about empty rulesets | warning |
| importStatement | Warn about using an import statement as import statements are loaded sequentially which has a negative impact on web page performance | ignore |
| boxModel | Do not use width or height when using padding or border | ignore |
| universalSelector | Warn when using the universal selector * as it is known to be slow and should be avoided | ignore |
| zeroUnits | Warn when having zero with a unit e.g. 0em as zero does not need a unit. | ignore |
| fontFaceProperties | Warn when using @font-face rule without defining a src and font-family property | 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. rgb | error |
| unknownProperties | Warn when using an unknown property | warning |
| ieHack | Warn when using an IE hack *propertyName or _propertyName | 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 display: inline , the width , height , margin-top , margin-bottom , and float properties have no effect. | warning |
| important | Warn when using !important as it is an indication that the specificity of the entire CSS has gotten out of control and needs to be refactored. | ignore |
| float | Warn when using float as floats lead to fragile CSS that is easy to break if one aspect of the layout changes. | ignore |
| idSelector | Warn when using selectors for an id #id as selectors should not contain IDs because these rules are too tightly coupled with the HTML. | ignore |
Next steps
Read on to find out about:
-
— Dig into Tasks to help you transpile your SCSS and Less to CSS. — Learn about the powerful VS Code editor. — Move quickly through your source code. — CSS is just the start, HTML is also very well supported in VS Code.
Common questions
Does VS Code provide a color picker?
Yes, hover over a CSS color reference and the color picker is displayed.
Is there support for the indentation based Sass syntax (.sass)?
No, but there are several extensions in the Marketplace supporting the indented flavor of Sass, for example, the Sass extension originally created by Robin Bentley, now maintained by Leonard Grosoli.
Sass в коде Visual Studio | Часть 1
Вы, наверное, слышали о препроцессорах CSS, таких как Sass, LESS или Stylus, и все они являются отличными инструментами для поддержания вашего CSS в актуальном состоянии, особенно при работе с большими базами кода. Для непосвященных вот краткое изложение:
Если у вас есть некоторые знания CSS, хорошо, если вы начали изучать sass.
В этой статье я остановлюсь на Sass. На сегодняшний день это наиболее широко используемый препроцессор. Я объясню, что такое Sass и как скомпилировать его в стандартный CSS, а также некоторые функции, которые делают его таким эффективным.
Что такое SASS?
Sass — это препроцессор для CSS. Sass уменьшает дублирование CSS и тем самым экономит время. CSS интересен сам по себе, но таблицы стилей становятся больше, сложнее и сложнее в управлении. Препроцессор может помочь в этой ситуации. Sass позволяет вам использовать функции, которых еще нет в CSS, такие как переменные, вложение, микширование, наследование и другие полезные функции, которые делают написание CSS более приятным.
Если мы используем бутстрап, мы можем использовать только несколько цветов для нашего проекта. Например, мы можем использовать синий цвет в качестве основного, но как мы используем фиолетовый цвет для нашего проекта. Итак, мы можем использовать SASS для этого. Не только фиолетовый, мы также можем использовать любой подобный цвет. Это особенность SASS.
Самый простой способ сделать это — в вашем терминале. Вы можете использовать команду sass для компиляции вашего Sass в CSS после его установки. Вам нужно будет сообщить Sass, куда выводить CSS и из какого файла создавать.
SASS против SCSS
- SCSS (он же Sassy CSS) — это современный стандарт. Его синтаксис очень похож на CSS в том, что он использует скобки и точки с запятой. Даже обычный CSS действителен в этом синтаксисе. Расширение файла .scss
- Sass — это более старый синтаксис, который фокусируется на отступах для разделения блоков кода и символов новой строки для разделения правил. Он имеет расширение файла .sass.
Но эти два выхода одинаковы. В этой статье я буду использовать SCSS, потому что это более естественный синтаксис. Он также отлично подходит для преобразования стандартного CSS в SCSS, так что вы можете только вставить CSS и начать работать!
Как мы устанавливаем Sass в наш проект Visual Studio Code
Прежде чем мы начнем, вы должны включить npm на своем компьютере; он включен в Node.js и может быть загружен здесь.
Установите его сейчас, если вы еще этого не сделали. Если вы не уверены, какой Node.js установлен, введите
в вашем терминале. Он установлен, если вы видите номер версии!
Затем откройте свой проект в коде VS и инициализируйте наш проект, используя
команда. если вы нажмете кнопку «Ввод», они спросят у вас некоторые вопросы, такие как имя пакета, версия, текстовая команда «Описание», например мудрый. Вы можете заполнить его как ваша страсть. наконец, вы нажимаете Enter, вы можете увидеть файл package.json в своем проекте.
Откройте файл json вашего пакета, вы можете найти имя пакета, версию и другую информацию, которую вы создали ранее.
Теперь вы можете установите sass в свой проект.
в вашем терминале, чтобы установить sass в глобальном
Затем создайте папку sass и создайте в ней файл sass (style.scss)
Затем снова перейдите к файлу package.json и создайте атрибут «start»
Здесь мы указали style.scss в качестве основного файла Sass и style.css в качестве скомпилированного файла CSS.
Также хорошей идеей будет наличие в вашем скрипте флага — watch. Флаг наблюдения указывает компилятору следить за исходными файлами на предмет улучшений и автоматически перекомпилировать в CSS, если вы сохраните файлы Sass. Пересохраните скрипт после добавления — смотрите.
Наконец, перейдите к своему терминалу и введите
и запустите свой код.
Теперь вы можете видеть, что файлы style.css и style.css.map создаются автоматически.
Что такое style.css.map?
Это Less можно использовать для создания загрузочного CSS. Основная цель файла карты — сравнить исходный код css с меньшим исходным кодом в инструменте разработчика Chrome. Раньше мы так делали. В инструменте разработчика Chrome мы можем проверить эту функцию. Исходный код CSS можно просмотреть. Однако, если файл карты используется на странице с файлом bootstrap css. Можно увидеть меньше кода, относящегося к стилю элемента, который вы хотите проверить.
Name already in use
vscode-docs / docs / languages / css.md
- Go to file T
- Go to line L
- Copy path
- Copy permalink
8 contributors
Users who have contributed to this file
- Open with Desktop
- View raw
- Copy raw contents Copy raw contents
Copy raw contents
Copy raw contents
CSS, SCSS and Less
Visual Studio Code has built-in support for editing style sheets in CSS .css , SCSS .scss and Less .less . In addition, you can install an extension for greater functionality.
Tip: Click on an extension tile above to read the description and reviews to decide which extension is best for you. See more in the Marketplace.
VS Code has support for selectors, properties and values. Use kb(editor.action.triggerSuggest) to get a list of context specific options.
Proposals contain extensive documentation, including a list of browsers that support the property. To see the full description text of the selected entry, use kb(toggleSuggestionDetails) .
Syntax coloring & color preview
As you type, there is syntax highlighting as well as in context preview of colors.
Clicking on a color preview will launch the integrated color picker which supports configuration of hue, saturation and opacity.
Tip: You can trigger between different color modes by clicking on the color string at the top of the picker.
You can hide VS Code’s color previews by setting the following setting:
To just disable it for css, Less and SCSS, use
You can fold regions of source code using the folding icons on the gutter between line numbers and line start. Folding regions are available for all declarations (for example, rule declarations) and for multiline comments in the source code.
Additionally you can use the following region markers to define a folding region: /*#region*/ and /*#endregion*/ in CSS/SCSS/Less or // #region and // #endregion In SCSS/Less.
If you prefer to switch to indentation based folding for CSS, Less and SCSS, use:
Emmet abbreviation support is built into VS Code, suggestions are listed along with other suggestions and snippets in the editor auto-completion list.
Tip: See the CSS section of the Emmet cheat sheet for valid abbreviations.
Syntax Verification & Linting
There is support for CSS version <= 2.1, Sass version <= 3.2 and Less version <= 2.3.
Note: You can disable VS Code’s default CSS, Sass or Less validation by setting the corresponding .validate User or Workspace setting to false.
Go to Symbol in file
You can quickly navigate to the relevant CSS symbol in the current file by pressing kb(workbench.action.gotoSymbol) .
Hovering over a selector or property will provide an HTML snippet that is matched by the CSS rule.
Go to Declaration and Find References
This is supported for Sass and Less variables in the same file. CSS variables per the draft standards proposal are also supported.
There is jump to definition for @import and url() links in CSS, SCSS and Less.
CSS custom data
You can extend VS Code’s CSS support through a declarative custom data format. By setting css.customData to a list of JSON files following the custom data format, you can enhance VS Code’s understanding of new CSS properties, at-directives, pseudo-classes and pesudo-elements. VS Code will then offer language support such as completion & hover information for the provided properties, at-directives, pseudo-classes and pesudo-elements.
You can read more about using custom data in the vscode-custom-data repository.
The CSS Languages Features extension also provides a formatter. The formatter works with CSS, LESS and SCSS. It is implemented by the JS Beautify library and comes with the following settings:
- css.format.enable — Enable/disable default CSS formatter.
- css.format.newlineBetweenRules — Separate rulesets by a blank line.
- css.format.newlineBetweenSelectors — Separate selectors with a new line.
- css.format.spaceAroundSelectorSeparator — Ensure a space character around selector separators ‘>’, ‘+’, ‘
The same settings also exist for less and scss .
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 .scss or .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 sass or less Node.js module.
Note: If you don’t have Node.js and the npm package manager already installed, you’ll need to do so for this walkthrough. Install Node.js for your platform. The Node Package Manager (npm) is included in the Node.js distribution. You’ll need to open a new terminal (command prompt) for npm to be on your PATH.
Step 2: Create a simple Sass or Less file
Open VS Code on an empty folder and create a styles.scss or styles.less file. Place the following code in that file:
For the Less version of the above file, just change $padding to @padding .
Note: This is a very simple example, which is why the source 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, run Terminal > Configure Tasks and click Create tasks.json file from template. In the selection dialog that shows up, select Others.
This will create a sample tasks.json file in the workspace .vscode folder. The initial version of file has an example to run an arbitrary command. We will modify that configuration for transpiling Sass/Less instead:
Step 4: Run the Build Task
As this is the only command in the file, you can execute it by pressing kb(workbench.action.tasks.build) (Run Build Task). The sample Sass/Less file should not have any compile problems, so by running the task all that happens is a corresponding styles.css file is created.
Since in more complex environments there can be more than one build task we prompt you to pick the task to execute after pressing kb(workbench.action.tasks.build) (Run Build Task). In addition, we allow you to scan the output for compile problems (errors and warnings). Depending on the compiler, select an appropriate entry in the list to scan the tool output for errors and warnings. If you don’t want to scan the output, select Never scan the build output from the presented list.
At this point, you should see an additional file show up in the file list styles.css .
If you want to make the task the default build task to run execute Configure Default Build Task from the global Terminal menu and select the corresponding Sass or Less task from the presented list.
Note: If your build fails or you see an error message such as «An output directory must be specified when compiling a directory», be sure the filenames in your tasks.json match the filenames on disk. You can always test your build by running sass styles.scss styles.css from the command line.
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.
We need to install gulp both globally ( -g switch) and locally:
Note: gulp-sass and gulp-less are Gulp plug-ins for the sass and lessc modules we were using before. There are many other Gulp Sass and Less plug-ins you can use, as well as plug-ins for Grunt.
You can test that your gulp installation was successful by typing gulp -v in the terminal. You should see a version displayed for both the global (CLI) and local installations.
Step 2: Create a simple Gulp task
Open VS Code on the same folder from before (contains styles.scss / styles.less and tasks.json under the .vscode folder), and create gulpfile.js at the root.
Place the following code in the gulpfile.js file:
What is happening here?
- Our default gulp task first runs the sass or less task once when it starts up.
- It then watches for changes to any SCSS/Less file at the root of our workspace, for example the current folder open in VS Code.
- It takes the set of SCSS/Less files that have changed and runs them through our respective compiler, for example gulp-sass , gulp-less .
- We now have a set of CSS files, each named respectively after their original SCSS/Less file. We then put these files in the same directory.
Step 3: Run the gulp default task
To complete the tasks integration with VS Code, we will need to modify the task configuration from before to run the default Gulp task we just created. You can either delete the tasks.json file or empty it only keeping the «version»: «2.0.0» property. Now execute Run Task from the global Terminal menu. Observe that you are presented with a picker listing the tasks defined in the gulp file. Select gulp: default to start the task. We allow you to scan the output for compile problems. Depending on the compiler, select an appropriate entry in the list to scan the tool output for errors and warnings. If you don’t want to scan the output, select Never scan the build output from the presented list. At this point, if you create and/or modify Less or SASS files, you 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 make the gulp: default task the default build task executed when pressing kb(workbench.action.tasks.build) run Configure Default Build Task from the global Terminal menu and select gulp: default from the presented list.
Step 4: Terminate the gulp default Task
The gulp: default task runs in the background and watches for file changes to Sass/Less files. If you want to stop the task, you can use the Terminate Task from the global Terminal menu.
Customizing CSS, SCSS and Less Settings
You can configure the following lint warnings as User and Workspace Settings.
The validate setting allows you turn off the built-in validation. You would do this if you rather use a different linter.
| Id | Description | Default |
|---|---|---|
| css.validate | Enables or disables all css validations | true |
| less.validate | Enables or disables all less validations | true |
| scss.validate | Enables or disables all scss validations | true |
To configure an option for CSS, use css.lint. as the prefix to the id; for SCSS and Less, use scss.lint. and less.lint. .
Set a setting to warning or error if you want to enable lint checking, use ignore to disable it. Lint checks are performed as you type.
| Id | Description | Default |
|---|---|---|
| validate | Enables or disables all validations | true |
| compatibleVendorPrefixes | When using a property with a vendor-specific prefix (for example -webkit-transition ), make sure to also include all other vendor-specific properties e.g. -moz-transition , -ms-transition and -o-transition | ignore |
| vendorPrefix | When using a property with a vendor-specific prefix for example -webkit-transition , make sure to also include the standard property if it exists e.g. transition | warning |
| duplicateProperties | Warn about duplicate properties in the same ruleset | ignore |
| emptyRules | Warn about empty rulesets | warning |
| importStatement | Warn about using an import statement as import statements are loaded sequentially which has a negative impact on web page performance | ignore |
| boxModel | Do not use width or height when using padding or border | ignore |
| universalSelector | Warn when using the universal selector * as it is known to be slow and should be avoided | ignore |
| zeroUnits | Warn when having zero with a unit e.g. 0em as zero does not need a unit. | ignore |
| fontFaceProperties | Warn when using @font-face rule without defining a src and font-family property | 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. rgb | error |
| unknownProperties | Warn when using an unknown property | warning |
| ieHack | Warn when using an IE hack *propertyName or _propertyName | 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 display: inline , the width , height , margin-top , margin-bottom , and float properties have no effect. | warning |
| important | Warn when using !important as it is an indication that the specificity of the entire CSS has gotten out of control and needs to be refactored. | ignore |
| float | Warn when using float as floats lead to fragile CSS that is easy to break if one aspect of the layout changes. | ignore |
| idSelector | Warn when using selectors for an id #id as selectors should not contain IDs because these rules are too tightly coupled with the HTML. | ignore |
Read on to find out about:
-
— Dig into Tasks to help you transpile your SCSS and Less to CSS. — Learn about the powerful VS Code editor. — Move quickly through your source code. — CSS is just the start, HTML is also very well supported in VS Code.
Does VS Code provide a color picker?
Yes, hover over a CSS color reference and the color picker is displayed.
Is there support for the indentation based Sass syntax (.sass)?
No, but there are several extensions in the Marketplace supporting the indented flavor of Sass, for example, the Sass extension originally created by Robin Bentley, now maintained by Leonard Grosoli.