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
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 package provides shared defaults for the tools this repo currently ships:
- Oxlint
- Prettier
- TypeScript
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"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...
}Create a tsconfig.json file in your project root with the following content:
{
"extends": ["@epic-web/config/typescript"],
"include": ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx"],
"compilerOptions": {
"paths": {
"#app/*": ["./app/*"],
"#tests/*": ["./tests/*"]
}
}
}Create a reset.d.ts file in your project with these contents:
import '@epic-web/config/reset.d.ts'Customizing TypeScript
Learn more from the TypeScript docs here.
Create a .oxlintrc.json file in your project root with the following content:
{
"extends": ["./node_modules/@epic-web/config/oxlint-config.json"]
}This config includes the custom epic-web/* rules documented in
lint-rules/index.md.
Note: typescript/no-misused-promises and typescript/no-floating-promises are
type-aware in Oxlint and require the type-aware setup described in the Oxlint
docs.
Some Oxlint rule IDs still use the eslint/ namespace because that is how
Oxlint exposes those compatibility rules. You do not need to install ESLint to
use them.
The following rule families are intentionally omitted because they are not yet part of the Oxlint config this package ships:
import/orderreact-hooks/rules-of-hooksreact-hooks/exhaustive-depstesting-library/*jest-dom/*- most
vitest/*rules playwright/*
MIT