ESLint Config by ElsiKora

Crafting Consistency, Nesting Best Practices, Enhancing Code Quality

Developed with the software and tools below.

Table of Contents

• Overview
• Features
• Repository Structure
• Modules
• Getting Started
  • Installation
  • Quick Setup (CLI)
  • Manual Setup
  • Example Config
• Project Roadmap
• Contributing
• License
• Acknowledgments

---

Overview

The ESLint-Config is a meticulously designed ESLint configuration repository that aims to enhance code quality and ensure consistency across JavaScript and TypeScript projects. Its core functionalities include custom ESLint rules, integration with popular plugins like Prettier and Unicorn, and specialized support for NestJS environments. By outlining standards for filename conventions and the use of modern JavaScript features, alongside automating the release process for streamlined updates, ESLint-Config offers a comprehensive solution for developers seeking to enforce coding best practices and style consistency in their projects.

---

Features

	Feature	Description
⚙️	Architecture	ESLint-Config is designed for JS/TS projects, integrating Prettier and Unicorn plugins.
🔩	Code Quality	Focuses on consistency & best practices by leveraging eslint, prettier, and custom ESLint rules.
📄	Documentation	Has basic documentation within code files and package.json, outlining usage and contributions.
🔌	Integrations	Integrates with GitHub Actions for CI/CD, Changesets for versioning, and Dependabot for updates.
🧩	Modularity	Configurations are modular, allowing easy extension and customization for JS/TS projects.
🧪	Testing	Comprehensive test coverage for configuration rules and plugin integrations.
⚡️	Performance	Optimized linting performance with selective rule application and caching support.
🛡️	Security	Regular dependency updates via Dependabot and security scanning in CI pipeline.
📦	Dependencies	Smart dependency management with automated updates and compatibility checks.
🚀	Scalability	Scalable through the addition of custom rules and extensions for various JavaScript environments.

---

Repository Structure

1└── ESLint-Config/
2    ├── .github
3    │   └── workflows
4    ├── .changeset
5    │   └── config.js
6    ├── CHANGELOG.md
7    ├── README.md
8    ├── index.enums.ts
9    ├── nest.js
10    └── package.json

---

Getting Started

Installation

Install configuration package:

1$ npm install @elsikora/eslint-config --save-dev

Quick Setup (CLI)

The easiest way to set up ESLint configuration is using our interactive CLI:

1$ npx @elsikora/eslint-config@latest

The CLI will:

1. Guide you through feature selection (JavaScript, TypeScript, React, etc.)
2. Set up ESLint configuration
3. Configure Prettier (optional)
4. Configure Stylelint (optional)
5. Set up IDE configurations (VSCode, WebStorm)
6. Configure GitHub CI workflows (optional)
   • Automated testing and linting
   • Release management with Changesets
   • Dependabot for dependency updates
7. Create all necessary configuration files

Manual Setup

If you prefer manual setup, create an .eslintrc.json file in your project root with one of these configurations:

For JavaScript projects:

1{
2  "extends": "@elsikora/eslint-config"
3}

For TypeScript projects:

1{
2  "extends": "@elsikora/eslint-config/typescript"
3}

For NestJS projects:

1{
2  "extends": "@elsikora/eslint-config/nest"
3}

For React projects:

1{
2  "extends": "@elsikora/eslint-config/react"
3}

For JSON:

1{
2  "extends": "@elsikora/eslint-config/json"
3}

For Yaml:

1{
2  "extends": "@elsikora/eslint-config/yaml"
3}

Example Config

Complete .eslintrc.json example with all features:

1{
2  "env": {
3    "es6": true,
4    "jest": true,
5    "node": true
6  },
7  "extends": [
8    "@elsikora/eslint-config",
9    "@elsikora/eslint-config/typescript",
10    "@elsikora/eslint-config/nest",
11    "@elsikora/eslint-config/react",
12    "@elsikora/eslint-config/json",
13    "@elsikora/eslint-config/yml"
14  ],
15  "ignorePatterns": [
16    ".eslintrc.json"
17  ],
18  "overrides": [
19    {
20      "files": [
21        "*.ts"
22      ],
23      "parser": "@typescript-eslint/parser",
24      "parserOptions": {
25        "ecmaVersion": "latest",
26        "sourceType": "module",
27        "project": "tsconfig.json",
28        "tsconfigRootDir": "./"
29      }
30    }
31  ],
32  "settings": {
33    "import/parsers": {
34      "@typescript-eslint/parser": [
35        ".ts",
36        ".tsx"
37      ]
38    },
39    "import/resolver": {
40      "typescript": {
41        "alwaysTryTypes": true,
42        "project": "./tsconfig.json"
43      }
44    }
45  },
46  "root": true
47}

---

Project Roadmap

• ► Interactive CLI Setup
• ► NestJS Configuration
• ► React Configuration
• ► Changesets Integration
• ► GitHub CI Workflows
• ► Next.js Configuration
• ► Angular Configuration
• ► Vue Configuration

---

Contributing

Contributions are welcome! Here are several ways you can contribute:

• Report Issues: Submit bugs found or log feature requests.
• Submit Pull Requests: Review open PRs, and submit your own PRs.
• Join the Discussions: Share your insights, provide feedback, or ask questions.

Contributing Guidelines

1. Fork the Repository: Start by forking the project repository to your GitHub account.
2. Clone Locally: Clone the forked repository to your local machine using a git client.

   1git clone https://github.com/ElsiKora/ESLint-Config.git

3. Create a New Branch: Always work on a new branch, giving it a descriptive name.

   1git checkout -b new-feature-x

4. Make Your Changes: Develop and test your changes locally.
5. Commit Your Changes: Commit with a clear message describing your updates.

   1git commit -m 'Implemented new feature x.'

6. Push to GitHub: Push the changes to your forked repository.

   1git push origin new-feature-x

7. Submit a Pull Request: Create a PR against the original project repository. Clearly describe the changes and their motivations.
8. Review: Once your PR is reviewed and approved, it will be merged into the main branch.

---

License

This project is protected under the MIT License. For more details, refer to the LICENSE file.

---

Acknowledgments

Thanks to all contributors and users of this configuration package. Special thanks to the ESLint and Prettier teams for their amazing tools.

Return