npm install @epic-web/config

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 is a set of configurations you can use in your web projects to avoid wasting time.

You can learn about the different decisions made for this project in the decision docs.

Technically you configure everything yourself, but you can use the configs in this project as a starter for your projects (and in some cases you don't need to configure anything more than the defaults).

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

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

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

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

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

{
	"extends": ["@epic-web/config/typescript"],
	"include": [
		"@epic-web/config/reset.d.ts",
		"**/*.ts",
		"**/*.tsx",
		"**/*.js",
		"**/*.jsx"
	],
	"compilerOptions": {
		"paths": {
			"#app/*": ["./app/*"],
			"#tests/*": ["./tests/*"]
		}
	}
}

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

import { config as defaultConfig } from '@epic-web/config/eslint'

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

There are endless rules we could enable. However, we want to keep our configurations minimal and only enable rules that catch real problems (the kind that are likely to happen). This keeps our linting faster and reduces the number of false positives.

MIT