neovim-flake/docs/manual/quirks/nodejs.md
NotAShelf 8a1ef233eb
docs: fix headings; move quirks to includes block'
Signed-off-by: NotAShelf <raf@notashelf.dev>
Change-Id: Ie853fc60a60c6ff6a945dc67560639ac6a6a6964
2025-12-18 16:34:08 +03:00

1.1 KiB

NodeJS

eslint-plugin-prettier

When working with NodeJS, which is obviously known for its meticulous standards, most things are bound to work as expected but some projects, tools and settings may fool the default configurations of tools provided by nvf.

If

If eslint-plugin-prettier or similar is included, you might get a situation where your Eslint configuration diagnoses your formatting according to its own config (usually .eslintrc.js). The issue there is your formatting is made via prettierd.

This results in auto-formatting relying on your prettier configuration, while your Eslint configuration diagnoses formatting "issues" while it's not supposed to. In the end, you get discrepancies between what your editor does and what it wants.

Solutions are:

  1. Don't add a formatting config to Eslint, instead separate Prettier and Eslint.
  2. PR the repo in question to add an ESLint formatter, and configure nvf to use it.