Package Exports
- eslint-plugin-html
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (eslint-plugin-html) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
eslint-plugin-html
This ESLint
plugin extracts and lints scripts from HTML files.
Supported HTML extensions: .html
, .xhtml
, .htm
, .xml
, .vue
, .hbs
, .mustache
, .handelbars
, .php
, .twig
Only script tags with no type attribute or a type attribute containing a MIME type known to represent JavaScript such as text/javascript
or application/javascript
, or text/babel
will be linted.
Usage
Simply install via npm npm install eslint-plugin-html --save
add the plugin to your ESLint configuration. See
ESLint documentation.
Example:
{
"plugins": [
"html"
]
}
Settings
html/indent
By default, the code between <script>
tags is dedented according to the first non-empty line. The
setting html/indent
allows to ensure that every script tags follow an uniform indentation. Like
the indent
rule, you can pass a number of spaces, or "tab"
to indent with one tab. Prefix this
value with a +
to be relative to the <script>
tag indentation. Example:
{
"plugins": [ "html" ],
"settings": {
"html/indent": "0", // code should start at the beginning of the line (no initial indentation).
"html/indent": "+2", // indentation is the <script> indentation plus two spaces.
"html/indent": "tab", // indentation is one tab at the beginning of the line.
}
}
html/report-bad-indent
By default, this plugin won't warn if it encounters a problematic indentation (ex: a line is under
indented). If you want to make sure the indentation is correct, use the html/report-bad-indent
in
conjunction with the indent
rule. Pass 1
to display warnings, or 2
to display errors. Example:
{
"plugins": [ "html" ],
"settings": {
"html/report-bad-indent": 2,
}
}
html/xml-mode
By default, files with an extension known to be XML (.xml
, .xhtml
) will be considered as XML.
This slightly changes the markup parsing, mainly when considering CDATA
sections:
- in XML, any data inside a
CDATA
section will be considered as raw text (not XML) and theCDATA
delimiter will be droped ; - in HTML, there is no such thing for
<script>
tags: theCDATA
delimiter is considered as normal text and thus, part of the script.
The setting html/xml-mode
allows to force all files to be considered as XML (by passing true
) or
HTML (by passing false
). Example:
{
"plugins": [ "html" ],
"settings": {
"html/xml-mode": true,
}
}