prettier-eslint VS gts

Use the other one, prettier-eslint this is so that the code goes through Prettier before ESLint and not the other way around causing it to show issues that will be fixed once ESLint fixes it.

Same, I can't stand some of prettier's opinions/style conversions and they refuse to add more options to their config file, so people literally have to make an entirely separate plugin just to deal with the issue of its config not being able to match your eslint config.

prettier-eslint

side note: you can use prettier-eslint (as opposed to the prettier eslint plugin) which runs prettier and then eslint --fix. that way you won't get annoyed by a shit ton red lines from eslint linting with prettier.

And I just ripped out my prettierrc/prettier recently, and still need some tweaking in this area, and might even add it it back. After looking at that plugin, it looks like it just DISABLES things in ESLint that Prettier handles, so you might have to add the prettier script and a .prettierrc config file. At least that is how I understand it. I was just looking at prettier's docs and saw this though - https://github.com/prettier/prettier-eslint, which seems like it might be what you are looking for.

// 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