template VS eslint-plugin-prettier

You can find the code behind it here on github. The underlying framework is a Typescript combination of Serverless Framework and CDK. I used the library swarmion to bootstrap the project and have a nice repository ready for deployment, check them out! Anyway, the code and deployment method are not very important here, as sls-mentor is framework agnostic.

If you plan to go on a monorepo architecture, you can already use Swarmion to create high scalable serverless application including Next.js latest version by simply running: pnpm create swarmion-app and choosing the Next.js option.

At Kumo, we build fullstack applications using Serverless and TypeScript. During our multiple projects, we encountered the problem of varying interfaces a lot. That is why we decided to build Swarmion, a tool to build stable serverless application at scale.

At Kumo, we have worked on developing an awesome tool to achieve just that: a complete and stable typescript stack to build serverless applications. Did you know? Our plugin integrates seamlessly with Swarmion, a framework for Serverless Typescript microservices.

Be sure to check out https://www.swarmion.dev/ for docs about Swarmion, the template repo and the tools repo. Any feedback is welcome!

Let's be honest - setting up tools for a new project can be a frustrating process. Especially when you want to jump straight to coding part. This is often the case with ESLint and Prettier, two popular tools in the JavaScript ecosystem that can sometimes interfere with each other when it comes to code formatting. Fortunately, there's a simple solution to this process, and it's called eslint-plugin-prettier.

You can also add ESLint now (props to @femincan for the suggestion). It comes with recommended settings for these plugins: typescript, prettier, react, react-hooks, jsx-a11y.

I recommend installing and configuring the eslint-plugin-prettier package in your project: https://github.com/prettier/eslint-plugin-prettier

eslint-plugin-prettier

Another approach that you can also take is a sort of "prettier as an ESLint plugin" option, such with eslint-plugin-prettier. The idea is that the developer only needs to run one tool (ESLint), but you add a plugin to ESLint that just calls prettier and converts the prettier error messages to ESLint error messages. I've worked at companies that have used this approach, and it makes setting up your editor/IDE very simple, because you've only got one tool to configure. That said, I personally don't like it because it forces you to use ESLint's "auto fix" functionality, which I find works well for formatting, but IME less well for some of the other lints.

A comprehensive set of formatting (through eslint-plugin-prettier) and linting rules, generated with Clinter. Once again, each package can easily extend the root configuration.

The eslint-config-prettier package disables all ESLint rules that might conflict with Prettier. This lets us use ESLint configurations without letting it get in the way when using Prettier. We can then use the eslint-plugin-prettier package to integrate Prettier rules into ESLint rules. Finally, we must set the Prettier rules in the ESLint configuration file. Add the following configuration to the .eslintrc file in the root directory of the application:

We run prettier through eslint, and run eslint through jest which provides parallelism. eslint also has a cache... So I'm not sure what dprint gets you over that?

https://github.com/jest-community/jest-runner-eslint

https://github.com/prettier/eslint-plugin-prettier

I personally use eslint-plugin-prettier so Prettier formatting issues are shown in my editor and are reported when linting using ESLint.

When installing the Prettier and ESLint extensions for VSCode, formatting and linting will also work within VSCode for any files in the monorepo. Only tweak required to make this work is to configure the Prettier plugin for ESLint (see example .eslintrc.json). Otherwise Prettier and ESLint will get in each other’s way and make for a poor editing experience. To make this work, the following two settings will also need to be configured in a .vscode/settings.json configuration (see settings.json):