https://github.com/ziyadedher/eslint-config

🛠🚀 Ziyad's ESLint configuration for hypermodern web development (TypeScript + Next.js + TailwindCSS)
https://github.com/ziyadedher/eslint-config

eslint eslint-config jest linter linter-config nextjs react tailwindcss typescript webdev

Last synced: 1 day ago
JSON representation

🛠🚀 Ziyad's ESLint configuration for hypermodern web development (TypeScript + Next.js + TailwindCSS)

• Host: GitHub
• URL: https://github.com/ziyadedher/eslint-config
• Owner: ziyadedher
• License: unlicense
• Created: 2021-09-07T02:23:48.000Z (about 3 years ago)
• Default Branch: main
• Last Pushed: 2024-10-21T06:39:39.000Z (18 days ago)
• Last Synced: 2024-10-21T09:35:45.072Z (18 days ago)
• Topics: eslint, eslint-config, jest, linter, linter-config, nextjs, react, tailwindcss, typescript, webdev
• Language: JavaScript
• Homepage:
• Size: 209 MB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 13
• Metadata Files:
  • Readme: README.md
  • License: LICENSE.md

Awesome Lists containing this project

README

        
# eslint-config-ziyad

🛠🚀 Ziyad's ESLint configuration for hypermodern web development (TypeScript + Next.js + TailwindCSS).

This is part of a larger effort to streamline the process of very quickly spinning up high-quality webapp projects (mostly for myself). A link to more information will eventually land here.

## Philosophy

I really like [Black](https://github.com/psf/black)'s concept of an uncompromising Python code formatter. There are three major tenants of the philosophy this configuration follows:

1. Eliminate the need to think about the minutiae of code style.

1. Provide a universal, easy-to-follow style guide for new projects.

1. Encourage the use of well-build modern technologies.

## Rules

Check out the [.eslintrc.yaml](.eslintrc.yaml) for the most up-to-date view of what rules and plugins are enabled.

Notably, this config _does not_ introduce any new rules. It just configures existing ones.

## Versioning

This projects follows a modified [semantic versioning](https://semver.org/) scheme for major, minor, and patch releases.

- Major: a technology change (addition or removal), or otherwise completely backwards-incompatible change.

- Minor: a rule or dependency change that may be backwards-incompatible _and_ does not have an automated fix.

- Patch: a rule or dependency change that is either backwards-compatible _or_ has an automated fix.