Skip to content

pycolors-io/pycolors-eslint-config

Repository files navigation

npm license

@pycolors/eslint-config

⚠️ Read-only mirror

This repository is automatically synced from the PyColors monorepo.
Source of truth: https://github.com/pycolors-io/pycolors/tree/main/packages/eslint-config

👉 Please open issues and pull requests here --- they are synced upstream.

Production-ready ESLint configurations for modern TypeScript and React applications.

Designed to enforce consistent code quality, predictable patterns, and scalable architecture across the PyColors ecosystem.


Why this exists

Most teams waste time reinventing lint rules.

PyColors provides a battle-tested baseline so you can focus on shipping product --- not debating formatting rules.

This config is optimized for:

  • Next.js apps
  • React libraries
  • Turborepo monorepos
  • TypeScript-first codebases

Install

pnpm add -D @pycolors/eslint-config eslint
# or
npm install -D @pycolors/eslint-config eslint

Usage

Next.js

Create an eslint.config.mjs:

import { nextJsConfig } from "@pycolors/eslint-config/next-js";

export default nextJsConfig;

React library

import { config } from "@pycolors/eslint-config/react-internal";

export default config;

Base config

import { config } from "@pycolors/eslint-config/base";

export default config;

What's inside

This package bundles a curated set of rules:

  • ESLint recommended
  • TypeScript ESLint
  • React + Hooks
  • Next.js Core Web Vitals
  • Prettier compatibility
  • Turbo rules for monorepos
  • Only-warn plugin to reduce CI friction

The goal is simple:

👉 strict enough to prevent bugs
👉 practical enough to keep velocity high


Design philosophy

PyColors tools are built around one principle:

Consistency scales.

When every project shares the same lint foundation:

  • onboarding becomes faster
  • reviews become simpler
  • architecture becomes predictable

Versioning

This package follows Semantic Versioning.

  • 1.x → stable baseline
  • rule additions → minor
  • breaking rule changes → major

Roadmap

Planned improvements:

  • stricter TypeScript presets
  • security-focused rules
  • performance linting
  • optional formatting layer

License

MIT


Links

About

Production-ready ESLint configs for Next.js, React and TypeScript monorepos — designed to enforce consistency and help teams ship faster.

Topics

Resources

Stars

Watchers

Forks

Releases

Packages

Contributors

Languages