</div><divclass="appendix"><divclass="titlepage"><div><div><h1id="ch-plugins"class="title">AppendixA.Plugin specific quirks </h1></div></div></div><divclass="toc"><p><strong>Table of Contents</strong></p><dlclass="toc"><dt><spanclass="chapter"><ahref="plugins.html#ch-plugins-nodejs">NodeJS</a></span></dt></dl></div><p>At times, certain plugins refuse to play nicely. Be it as a result of generating
are known to misbehave, and potential workarounds.</p><divclass="chapter"><divclass="titlepage"><div><div><h2id="ch-plugins-nodejs"class="title">NodeJS </h2></div></div></div><divclass="toc"><p><strong>Table of Contents</strong></p><dlclass="toc"><dt><spanclass="section"><ahref="plugins.html#sec-eslint-plugin-prettier">eslint-plugin-prettier</a></span></dt></dl></div><divclass="section"><divclass="titlepage"><div><div><h2id="sec-eslint-plugin-prettier"class="title"style="clear: both">eslint-plugin-prettier </h2></div></div></div><p>When working with NodeJS, everything works as expected, but some projects have settings that can fool nvf.</p><p>If <aclass="link"href="https://github.com/prettier/eslint-plugin-prettier"target="_top">this plugin</a> or similar is included, you might get a situation where your eslint configuration diagnoses your formatting according to its own config (usually <codeclass="literal">.eslintrc.js</code>).</p><p>The issue there is your formatting is made via prettierd.</p><p>This results in auto-formating relying on your prettier config, while your eslint config diagnoses formatting <aclass="link"href="https://prettier.io/docs/en/comparison.html"target="_top">which it’s not supposed to</a>)</p><p>In the end, you get discrepancies between what your editor does and what it wants.</p><p>Solutions are:</p><divclass="orderedlist"><olclass="orderedlist compact"type="1"><liclass="listitem"><p>Don’t add a formatting config to eslint, and separate prettier and eslint.</p></li><liclass="listitem"><p>PR this repo to add an ESLint formatter and configure nvf to use it.</p></li></ol></div>
