PSA: Changes to ESLint & HTML mainly affecting Sublime Text users

Mark Banner mbanner at mozilla.com
Sat Jun 22 19:51:30 UTC 2019


tl;dr We've changed ESLint's configuration to enable HTML parsing by 
default for better editor integration. Sublime Text users will need to 
change configuration.

Up until now the ESLint configuration in mozilla-central has been with 
the html plugin not enabled, but to enable it when `./mach eslint` is 
run. The main effect of this is that editors that automatically run 
linters, HTML files would not be checked.

With the configuration change 
<https://bugzilla.mozilla.org/show_bug.cgi?id=1464007>, HTML files will 
now be parsed by VSCode and Atom (and possibly other editors).

The downside is that Sublime Text has its own parsing for HTML files and 
this conflicts with ESLint's HTML plugin 
<https://github.com/SublimeLinter/SublimeLinter-eslint/issues/253>.

If you want Sublime to keep working, you need to change your user 
settings for the SublimeLinter plugin to include the selector 
configuration below:

|{ "linters": { "eslint": { "selector": "source.js, text.html.basic, 
text.xml", } } } |||

Mark

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/firefox-dev/attachments/20190622/64aa07f4/attachment.html>


More information about the firefox-dev mailing list