<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>+1 for Marks's suggestion!</p>
<p>FMPOV addon authors should use an uncomplicated dev environment.
I moved to Atom for development of TB addon and enabled Linter
with linter-jshint packages. That does a good job and enables me
to see "old" errors. Additionally a small Pyhton script does the
XPI/ZIP generation. A lightweight installation, very effective!</p>
<p>Günter</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 19.10.18 10:12, Mark Banner wrote:<br>
</div>
<blockquote type="cite"
cite="mid:46dcb6b0-55f2-459b-2342-78d4e03b6e83@mozilla.com">Without
more information on the specifics, I'd suggest that promoting <a
moz-do-not-send="true" href="https://eslint.org/">ESLint</a> to
add-on authors is more likely to be useful - there's <a
moz-do-not-send="true" href="https://eslint.org/docs/rules/">lots
of rules</a> highlighting various issues that can be selectively
enabled. For legacy/hybrid add-ons, there's <a
moz-do-not-send="true"
href="https://www.npmjs.com/package/eslint-plugin-mozilla">eslint-plugin-mozilla</a>
which has the mozilla-central configuration, and useful rules
specific to gecko.</blockquote>
</body>
</html>