gts VS prettierd

// https://github.com/google/gts/blob/main/.prettierrc.json { "bracketSpacing": false, "singleQuote": true, "trailingComma": "es5", "arrowParens": "avoid" }

If you want to write apps that run on Node.js I would suggest using Google’s TypeScript style guide. You can start using it by simply running npx gts init. I’d suggest that you start with this and run your apps using ts-node/ts-node-dev because it does not require an extra build step.

To minize the effort gts is a nice tool to help you setting up the project. Our of deployment/devliver purposes we also want to bundle the code to create nice and small artifacts. For those purposes we use esbuild. The whole example can be found here

First, you need prettierd:

Besides remapping keys, auto-format with prettier (null-ls, ALE, etc) will wrap your code on line break. This might not be desirable for txt files, but it's transparent and fully supported by markdown. It'll also fix things like aligning your markdown tables. There's also prettierd and prettier_d_slim to keep it running as a daemon in the background, which makes the buffer reformatting really snappy.

For react you will need the one for typescript and the eslint lsp is also used in the config to auto fix errors on save. Also this relies on prettierd to be installed globally: https://github.com/fsouza/prettierd

But today I discovered this tool: https://github.com/fsouza/prettierd. This completely solves the issue: the slowness of prettier is due to the overhead of launching the program. This package leaves prettier running as a daemon, which removes the launch overhead (kind of similar to the already famous `eslint_d`).