Techmmunity - Style Guide

In this package, you can find the Techmmunity Style Guide. We try to keep a clean and consistent code style, with modern features and using best practices.

:warning: WARNING :warning:

This package may not be updated so often, but it not means that it has been abandoned. We do the config in a way to (almost) never have to touch it again, and we only update the package to add new features, what may don't need to happen so often.

Badges

[![Style Guide: Techmmunity](https://img.shields.io/badge/style%20guide-Techmmunity-01d2ce?style=plastic)](https://github.com/techmmunity/eslint-config)

[![Style Guide: Techmmunity](https://img.shields.io/badge/style%20guide-Techmmunity-01d2ce?style=flat)](https://github.com/techmmunity/eslint-config)

[![Style Guide: Techmmunity](https://img.shields.io/badge/style%20guide-Techmmunity-01d2ce?style=square)](https://github.com/techmmunity/eslint-config)

[![Style Guide: Techmmunity](https://img.shields.io/badge/style%20guide-TECHMMUNITY-01d2ce?style=for-the-badge)](https://github.com/techmmunity/eslint-config)

Why use this config?

• Best practices focused in modern features and principles (SOLID, DRY, KISS, Clean Code)
• Constant maintenance
• Ready-to-go: You don't need any extra config
• Bye bye prettier: You don't need to be using the prettier extension for VSCode if you have this baby on your project
• Direct support: Join our discord community and get your questions answered

Install

yarn add -D @techmmunity/eslint-config eslint prettier

Obs: If you are using VSCode, you may need/want to do some extra steps.

Basic Usage

1 - Create a .eslintrc.json file in the root of your project

2 - Put the following content inside the file:

{
	"root": true,
	"extends": "@techmmunity/eslint-config"
}

3 - Restart the VSCode, and it's done!

Need more examples?

We provide an example repository, you can give a look at it, or join our discord community and make some questions!

Modules

Alert: After any change at eslintrc.json file, you must restart VSCode.

Alert: The common module must ALWAYS be extend, and must ALWAYS be the fist one.

This repository contains the best practices divided by libs, frameworks and tools. The currently existent modules are:

The common module is the default rules used by every javascript project. It doesn't contains any special config for frameworks, backend, frontend or npm package. You must import this module if you want to use any of the other modules of this package.

Tip: You can see an example project here

Usage

Create an .eslintrc.json file in the root folder of your package and add this content to it:

{
	"root": true,
	"extends": "@techmmunity/eslint-config/common"
}

Specific configs to projects that uses Jest.

Usage

Create an .eslintrc.json file in the root folder of your package and add this content to it:

{
	"root": true,
	"extends": [
		"@techmmunity/eslint-config/common", // The common module always should be extended!
		"@techmmunity/eslint-config/jest"
	]
}

Specific configs to projects that uses NextJs.

Usage

Create an .eslintrc.json file in the root folder of your package and add this content to it:

{
	"root": true,
	"extends": [
		"@techmmunity/eslint-config/common", // The common module always should be extended!
		"@techmmunity/eslint-config/nextjs"
	]
}

Specific configs to projects that uses React.

Usage

Create an .eslintrc.json file in the root folder of your package and add this content to it:

{
	"root": true,
	"extends": [
		"@techmmunity/eslint-config/common", // The common module always should be extended!
		"@techmmunity/eslint-config/react"
	]
}

Specific configs to projects that uses NextJs with TypeScript.

Usage

Create an .eslintrc.json file in the root folder of your package and add this content to it:

{
	"root": true,
	"extends": [
		"@techmmunity/eslint-config/common", // The common module always should be extended!
		"@techmmunity/eslint-config/ts-nextjs"
	]
}

Specific configs to projects that uses React with TypeScript.

Usage

Create an .eslintrc.json file in the root folder of your package and add this content to it:

{
	"root": true,
	"extends": [
		"@techmmunity/eslint-config/common", // The common module always should be extended!
		"@techmmunity/eslint-config/ts-react"
	]
}

Specific configs for typescript projects.

Usage

Create an .eslintrc.json file in the root folder of your package and add this content to it:

{
	"root": true,
	"extends": [
		"@techmmunity/eslint-config/common", // The common module always should be extended!
		"@techmmunity/eslint-config/typescript"
	]
}

Combining Modules

You can safely combine some modules, like this:

{
	"root": true,
	"extends": [
		"@techmmunity/eslint-config/common", // The common module always should be extended!
		"@techmmunity/eslint-config/typescript",
		"@techmmunity/eslint-config/jest"
	]
}

But in some cases, where that module is already imported, it will cause a conflict, like in this case:

{
	"root": true,
	"extends": [
		"@techmmunity/eslint-config/common", // The common module always should be extended!
		"@techmmunity/eslint-config/nextjs"
	]
}

Warnings

Problems with Prettier

If you are using the VSCode Prettier Extension, you need to disable it, because this package already configs the prettier and uses it under the hood.

To disable Prettier, you just need to add this to your vscode configs:

{
	"[javascript]": {
		"editor.defaultFormatter": null
	},
	"[typescript]": {
		"editor.defaultFormatter": null
	},
	"[javascriptreact]": {
		"editor.defaultFormatter": null
	},
	"[typescriptreact]": {
		"editor.defaultFormatter": null
	}
}

You can access this configs by pressing Ctrl + Shift + P and tipping Preferences: Open Settings (JSON).

Extra - VSCode Tips & Tricks

See the errors and warnings

• Use Ctrl + Shift + X
• Search for dbaeumer.vscode-eslint
• Install the extension

Auto fix issues

• Use Ctrl + Shift + P
• Search for Preferences: Open Settings (JSON)
• Click in it
• Add this to the JSON:

// Make ESLint fix all the things that he can on save (like prettier formatting)
"editor.codeActionsOnSave": {
	"source.fixAll.eslint": true
},

Contribution

To test this package:

1. If you are testing and making chances, you may need run yarn unlink, but for your first time, you can ignore this
2. Run yarn lk
3. Go to a big project and run yarn link @techmmunity/eslint-config
4. And it's done! Just give a look at the project and see if everything is working like you want.

Tip: You can use npx eslint . to lint the project automatically