![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
@epic-web/config
Advanced tools
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 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"
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": [
"@epic-web/config/reset.d.ts",
"**/*.ts",
"**/*.tsx",
"**/*.js",
"**/*.jsx"
],
"compilerOptions": {
"paths": {
"#app/*": ["./app/*"],
"#tests/*": ["./tests/*"]
}
}
}
Learn more from the TypeScript docs here.
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]
Learn more from the Eslint docs here.
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
FAQs
Reasonable ESLint configs for epic web devs
The npm package @epic-web/config receives a total of 2,975 weekly downloads. As such, @epic-web/config popularity was classified as popular.
We found that @epic-web/config demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.