Support for Emmet snippets and expansion is built right into Visual Studio Code, no extension required. Emmet 2.0 has support for the majority of the Emmet Actions including expanding Emmet abbreviations and snippets.
Enable Run-Time Type Info — This option chooses whether or not to add code for checking C object types at run time. Use a separate Visual Studio instance to debug the host portion of a target application. If you wish to debug the host portion of your CUDA application while the CUDA Debugger is attached, you must attach using a different.
How to expand Emmet abbreviations and snippets
- Emmet in Visual Studio Code. Support for Emmet snippets and expansion is built right into Visual Studio Code, no extension required. Emmet 2.0 has support for the majority of the Emmet Actions including expanding Emmet abbreviations and snippets. How to expand Emmet abbreviations and snippets.
- By default, Visual Studio builds the web project when you run a page. Building the project helps you find compile-time errors before the page is displayed in the browser. You can set options to specify whether you want to build the entire project, the current page, or not build at all.
- Steps: Use ctrl + shift + p (or F1) to open the Command Palette. Type in Tasks: Configure Task or on older versions Configure Task Runner. Selecting it will open the tasks.json file. Switch back to your html file (in this example it's 'text.html'), and press ctrl + shift + b to view.
Emmet abbreviation and snippet expansions are enabled by default in html
, haml
, pug
, slim
, jsx
, xml
, xsl
, css
, scss
, sass
, less
and stylus
files, as well as any language that inherits from any of the above like handlebars
and php
.
When you start typing an Emmet abbreviation, you will see the abbreviation displayed in the suggestion list. If you have the suggestion documentation fly-out open, you will see a preview of the expansion as you type. If you are in a stylesheet file, the expanded abbreviation shows up in the suggestion list sorted among the other CSS suggestions.
Using Tab for Emmet expansions
If you want to use the Tab key for expanding the Emmet abbreviations, add the following setting:
This setting allows using the Tab key for indentation when text is not an Emmet abbreviation.
Emmet when quickSuggestions are disabled
If you have disabled the editor.quickSuggestions
setting, you won't see suggestions as you type. You can still trigger suggestions manually by pressing ⌃Space (Windows, Linux Ctrl+Space) and see the preview.
Disable Emmet in suggestions
If you don't want to see Emmet abbreviations in suggestions at all, then use the following setting:
You can still use the command Emmet: Expand Abbreviation to expand your abbreviations. You can also bind any keyboard shortcut to the command id editor.emmet.action.expandAbbreviation
as well.
Emmet suggestion ordering
To ensure Emmet suggestions are always on top in the suggestion list, add the following settings:
Emmet abbreviations in other file types
To enable the Emmet abbreviation expansion in file types where it is not available by default, use the emmet.includeLanguages
setting. Make sure to use language identifiers for both sides of the mapping, with the right side being the language identifier of an Emmet supported language (see the list above).
For example:
Emmet has no knowledge of these new languages, and so there might be Emmet suggestions showing up in non HTML/CSS contexts. To avoid this, you can use the following setting.
Note: If you used emmet.syntaxProfiles
previously to map new file types, from VS Code 1.15 onwards you should use the setting emmet.includeLanguages
instead. emmet.syntaxProfiles
is meant for customizing the final output only.
Emmet with multi-cursors
You can use most of the Emmet actions with multi-cursors as well:
Using filters
Filters are special post-processors that modify the expanded abbreviation before it is output to the editor. There are 2 ways to use filters; either globally through the emmet.syntaxProfiles
setting or directly in the current abbreviation.
Below is an example of the first approach using the emmet.syntaxProfiles
setting to apply the bem
filter for all the abbreviations in HTML files:
To provide a filter for just the current abbreviation, append the filter to your abbreviation. For example, div#page|c
will apply the comment
filter to the div#page
abbreviation.
BEM filter (bem)
If you use the Block Element Modifier (BEM) way of writing HTML, then bem
filters are very handy for you to use. To learn more about how to use bem
filters, read BEM filter in Emmet.
You can customize this filter by using the bem.elementSeparator
and bem.modifierSeparator
preferences as documented in Emmet Preferences.
Comment filter (c)
This filter adds comments around important tags. By default, 'important tags' are those tags with id and/or class attribute.
For example div>div#page>p.title+p|c
will be expanded to:
You can customize this filter by using the filter.commentTrigger
, filter.commentAfter
and filter.commentBefore
preferences as documented in Emmet Preferences.
The format for the filter.commentAfter
preference is different in VS Code Emmet 2.0.
For example, instead of:
in VS Code, you would use a simpler:
Trim filter (t)
This filter is applicable only when providing abbreviations for the Emmet: Wrap Individual Lines with Abbreviation command. It removes line markers from wrapped lines.
Using custom Emmet snippets
Custom Emmet snippets need to be defined in a json file named snippets.json
. The emmet.extensionsPath
setting should have the path to the directory containing this file.
Below is an example for the contents of this snippets.json
file.
Authoring of Custom Snippets in Emmet 2.0 via the snippets.json
file differs from the old way of doing the same in a few ways:
Topic | Old Emmet | Emmet 2.0 |
---|---|---|
Snippets vs Abbreviations | Supports both in 2 separate properties called snippets and abbreviations | The 2 have been combined into a single property called snippets. See default HTML snippets and CSS snippets |
CSS snippet names | Can contain : | Do not use : when defining snippet names. It is used to separate property name and value when Emmet tries to fuzzy match the given abbreviation to one of the snippets. |
CSS snippet values | Can end with ; | Do not add ; at end of snippet value. Emmet will add the trailing ; based on the file type (css/less/scss vs sass/stylus) or the emmet preference set for css.propertyEnd , sass.propertyEnd , stylus.propertyEnd |
Cursor location | ${cursor} or | can be used | Use only textmate syntax like ${1} for tab stops and cursor locations |
HTML Emmet snippets
HTML custom snippets are applicable to all other markup flavors like haml
or pug
. When snippet value is an abbreviation and not actual HTML, the appropriate transformations can be applied to get the right output as per the language type.
For example, for an unordered list with a list item, if your snippet value is ul>li
, you can use the same snippet in html
, haml
, pug
or slim
, but if your snippet value is <ul><li></li></ul>
, then it will work only in html
files.
If you want a snippet for plain text, then surround the text with {}
.
CSS Emmet snippets
Values for CSS Emmet snippets should be a complete property name and value pair.
CSS custom snippets are applicable to all other stylesheet flavors like scss
, less
or sass
. Therefore, don't include a trailing ;
at the end of the snippet value. Emmet will add it as needed based on whether the language requires it.
Do not use :
in the snippet name. :
is used to separate property name and value when Emmet tries to fuzzy match the abbreviation to one of the snippets.
Tab stops and cursors in custom snippets
The syntax for tab stops in custom Emmet snippets follows the Textmate snippets syntax.
- Use
${1}
,${2}
for tab stops and${1:placeholder}
for tab stops with placeholders. - Previously,
|
or${cursor}
was used to denote the cursor location in the custom Emmet snippet. This is no longer supported. Use${1}
instead.
Emmet configuration
Below are Emmet settings that you can use to customize your Emmet experience in VS Code.
emmet.includeLanguages
Use this setting to add mapping between the language of your choice and one of the Emmet supported languages to enable Emmet in the former using the syntax of the latter. Make sure to use language ids for both sides of the mapping.
For example:
emmet.excludeLanguages
If there is a language where you do not want to see Emmet expansions, add it in this setting which takes an array of language id strings.
emmet.syntaxProfiles
See Emmet Customization of output profile to learn how you can customize the output of your HTML abbreviations.
For example:
emmet.variables
Customize variables used by Emmet snippets.
For example:
emmet.showExpandedAbbreviation
Controls the Emmet suggestions that show up in the suggestion/completion list.
Setting Value Description never
Never show Emmet abbreviations in the suggestion list for any language. inMarkupAndStylesheetFilesOnly
Show Emmet suggestions only for languages that are purely markup and stylesheet based ('html', 'pug', 'slim', 'haml', 'xml', 'xsl', 'css', 'scss', 'sass', 'less', 'stylus'). always
Show Emmet suggestions in all Emmet supported modes as well as the languages that have a mapping in the emmet.includeLanguages
setting.Note: In the
always
mode, the new Emmet implementation is not context aware. For example, if you are editing a JavaScript React file, you will get Emmet suggestions not only when writing markup but also while writing JavaScript.emmet.showAbbreviationSuggestions
Shows possible emmet abbreviations as suggestions. It is
true
by default.For example, when you type
li
, you get suggestions for all emmet snippets starting withli
likelink
,link:css
,link:favicon
etc. This is helpful in learning Emmet snippets that you never knew existed unless you knew the Emmet cheatsheet by heart.Not applicable in stylesheets or when
emmet.showExpandedAbbreviation
is set tonever
.emmet.extensionsPath
Provide the location of the directory that houses the
snippets.json
file which in turn has your custom snippets.emmet.triggerExpansionOnTab
Set this to true to enable expanding Emmet abbreviations with Tab key. We use this setting to provide the appropriate fallback to provide indentation when there is no abbreviation to expand.
emmet.showSuggestionsAsSnippets
If set to
true
, then Emmet suggestions will be grouped along with other snippets allowing you to order them as pereditor.snippetSuggestions
setting. Set this totrue
andeditor.snippetSuggestions
totop
, to ensure that Emmet suggestions always show up on top among other suggestions.emmet.preferences
You can use this setting to customize Emmet as documented in Emmet Preferences. The below customizations are currently supported:
css.propertyEnd
css.valueSeparator
sass.propertyEnd
sass.valueSeparator
stylus.propertyEnd
stylus.valueSeparator
css.unitAliases
css.intUnit
css.floatUnit
bem.elementSeparator
bem.modifierSeparator
filter.commentBefore
filter.commentTrigger
filter.commentAfter
format.noIndentTags
format.forceIndentationForTags
profile.allowCompactBoolean
css.fuzzySearchMinScore
The format for the
filter.commentAfter
preference is different and simpler in Emmet 2.0.For example, instead of the older format
you would use
If you want support for any of the other preferences as documented in Emmet Preferences, please log a feature request.
Next steps
Emmet is just one of the great web developer features in VS Code. Read on to find out about:
- HTML - VS Code supports HTML with IntelliSense, closing tags, and formatting.
- CSS - We offer rich support for CSS, SCSS and Less.
Common questions
Custom tags do not get expanded in the suggestion list
Custom tags when used in an expression like MyTag>YourTag
or MyTag.someclass
do show up in the suggestion list. But when these are used on their own like MyTag
, they do not appear in the suggestion list. This is designed so to avoid noise in the suggestion list as every word is a potential custom tag.
Add the following setting to enable expanding of Emmet abbreviations using tab which will expand custom tags in all cases.
My HTML snippets ending with +
do not work?
HTML snippets ending with +
like select+
and ul+
from the Emmet cheatsheet are not supported. This is a known issue in Emmet 2.0 Issue: emmetio/html-matcher#1. Workaround is to create your own custom Emmet snippets for such scenarios.
Where can I set all the preferences as documented in Emmet preferences
You can set the preferences using the setting emmet.preferences
. Only a subset of the preferences that are documented in Emmet preferences can be customized. Please read the preferences section under Emmet configuration.
Any tips and tricks?
Of course!
- In CSS abbreviations, when you use
:
, the left part is used to fuzzy match with the CSS property name and the right part is used to match with CSS property value. Take full advantage of this by using abbreviations likepos:f
,trf:rx
,fw:b
, etc. - Use the new command Emmet: Wrap Individual Lines with Abbreviation instead of Emmet: Wrap with Abbreviation when you want each selected line to be wrapped by a repeater in the given abbreviation. For example, use
ul>li*
to wrap selected lines in an unordered list with each line as a list item. - Explore all other Emmet features as documented in Emmet Actions.
- Don't hesitate to create your own custom Emmet snippets.
Visual Studio Code provides basic support for HTML programming out of the box. There is syntax highlighting, smart completions with IntelliSense, and customizable formatting. VS Code also includes great Emmet support.
IntelliSense
As you type in HTML, we offer suggestions via HTML IntelliSense. In the image below, you can see a suggested HTML element closure </div>
as well as a context specific list of suggested elements.
We also offer up suggestions for elements, tags, some values (as defined in HTML5), Ionic and AngularJS tags. Document symbols are also available for HTML, allowing you to quickly navigate to DOM nodes by id and class name.
You can also work with embedded CSS and JavaScript. However, note that script and style includes from other files are not followed, the language support only looks at the content of the HTML file.
You can trigger suggestions at any time by pressing ⌃Space (Windows, Linux Ctrl+Space).
You can also control which built-in code completion providers are active. Override these in your user or workspace settings if you prefer not to see the corresponding suggestions.
Close tags
Tag elements are automatically closed when >
of the opening tag is typed.
The matching closing tag is inserted when /
of the closing tag is entered.
You can turn off autoclosing tags with the following setting:
Auto update tags
When modifying a tag, the linked editing feature automatically updates the matching closing tag. The feature is optional and can be enabled by setting:
Color picker
The VS Code color picker UI is now available in HTML style sections.
It supports configuration of hue, saturation and opacity for the color that is picked up from the editor. It also provides the ability to trigger between different color modes by clicking on the color string at the top of the picker. The picker appears on a hover when you are over a color definition.
Hover
Move the mouse over HTML tags or embedded styles and JavaScript to get more information on the symbol under the cursor.
Validation
The HTML language support performs validation on all embedded JavaScript and CSS.
You can turn that validation off with the following settings:
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 HTML elements for multiline comments in the source code.
Additionally you can use the following region markers to define a folding region: <!-- #region -->
and <!-- endregion -->
If you prefer to switch to indentation based folding for HTML use:
Formatting
Run Html File Visual Studio Code
To improve the formatting of your HTML source code, you can use the Format Document command ⇧⌥F (Windows Shift+Alt+F, Linux Ctrl+Shift+I) to format the entire file or Format Selection⌘K ⌘F (Windows, Linux Ctrl+K Ctrl+F) to just format the selected text.
The HTML formatter is based on js-beautify. The formatting options offered by that library are surfaced in the VS Code settings:
html.format.wrapLineLength
: Maximum amount of characters per line.html.format.unformatted
: List of tags that shouldn't be reformatted.html.format.contentUnformatted
: List of tags, comma separated, where the content shouldn't be reformatted.html.format.extraLiners
: List of tags that should have an extra newline before them.html.format.preserveNewLines
: Whether existing line breaks before elements should be preserved.html.format.maxPreserveNewLines
: Maximum number of line breaks to be preserved in one chunk.html.format.endWithNewline
: End with a newline.html.format.indentInnerHtml
: Indent<head>
and<body>
sections.html.format.wrapAttributes
: Wrapping strategy for attributes:auto
: Wrap when the line length is exceededforce
: Wrap all attributes, except firstforce-aligned
: Wrap all attributes, except first, and align attributesforce-expand-multiline
: Wrap all attributesaligned-multiple
: Wrap when line length is exceeded, align attributes verticallypreserve
: Preserve wrapping of attributespreserve-aligned
: Preserve wrapping of attributes but align
html.format.wrapAttributesIndentSize
: Alignment size when usingforce aligned
andaligned multiple
inhtml.format.wrapAttributes
ornull
to use the default indent size.html.format.templating
: Honor django, erb, handlebars and php templating language tags.html.format.unformattedContentDelimiter
: Keep text content together between this string.
Tip: The formatter doesn't format the tags listed in the html.format.unformatted
and html.format.contentUnformatted
settings. Embedded JavaScript is formatted unless 'script' tags are excluded.
The Marketplace has several alternative formatters to choose from. If you want to use a different formatter, define 'html.format.enable': false
in your settings to turn off the built-in formatter.
Emmet snippets
VS Code supports Emmet snippet expansion. Emmet abbreviations are listed along with other suggestions and snippets in the editor auto-completion list.
Tip: See the HTML section of the Emmet cheat sheet for valid abbreviations.
If you'd like to use HTML Emmet abbreviations with other languages, you can associate one of the Emmet modes (such as css
, html
) with other languages with the emmet.includeLanguages
setting. The setting takes a language id and associates it with the language id of an Emmet supported mode.
For example, to use Emmet HTML abbreviations inside JavaScript:
Execute Html File In Visual Studio Code
We also support User Defined Snippets.
HTML custom data
You can extend VS Code's HTML support through a declarative custom data format. By setting html.customData
to a list of JSON files following the custom data format, you can enhance VS Code's understanding of new HTML tags, attributes and attribute values. VS Code will then offer language support such as completion & hover information for the provided tags, attributes and attribute values.
You can read more about using custom data in the vscode-custom-data repository.
HTML extensions
Install an extension to add more functionality. Go to the Extensions view (⇧⌘X (Windows, Linux Ctrl+Shift+X)) and type 'html' to see a list of relevant extensions to help with creating and editing HTML.
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.
Next steps
Read on to find out about:
- CSS, SCSS, and Less - VS Code has first class support for CSS including Less and SCSS.
- Emmet - Learn about VS Code's powerful built-in Emmet support.
- Emmet official documentation - Emmet, the essential toolkit for web-developers.
Common questions
Does VS Code have HTML preview?
No, VS Code doesn't have built-in support for HTML preview but there are extensions available in the VS Code Marketplace. Open the Extensions view (⇧⌘X (Windows, Linux Ctrl+Shift+X)) and search on 'live preview' or 'html preview' to see a list of available HTML preview extensions.