@epic-web/config

👮 @epic-web/config

Reasonable ESLint, Prettier, and TypeScript configs for epic web devs

This makes assumptions about the way you prefer to develop software and gives you configurations that will actually help you in your development.

npm install @epic-web/config

---

The problem

You're a professional, but you're mature enough to know that even professionals can make mistakes and you value your time enough to not want to waste time configuring code quality tools or babysitting them.

This solution

This is a set of configurations you can use in your web projects to avoid wasting time.

Usage

Prettier

The easiest way to use this config is in your package.json:

"prettier": "@epic-web/config/prettier"

Customizing prettier

If you want to customize things, you should probably just copy/paste the built-in config. But if you really want, you can override it using regular JavaScript stuff.

Create a .prettierrc.js file in your project root with the following content:

import defaultConfig from '@epic-web/config/prettier'

/** @type {import("prettier").Options} */
export default {
	...defaultConfig,
	// .. your overrides here...
}

TypeScript

Create a tsconfig.json file in your project root with the following content:

{
	"extends": "@epic-web/config/typescript",
	"include": ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx"]
}

Customizing TypeScript

Learn more from the TypeScript docs here.

ESLint

Create a eslint.config.js file in your project root with the following content:

import defaultConfig from '@epic-web/config/eslint'

/** @type {import("eslint").Linter.Config} */
export default [...defaultConfig]

Customizing ESLint

Learn more from the Eslint docs here.

License

MIT