npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2025 – Pkg Stats / Ryan Hefner

@elsikora/eslint-config

v3.2.4

Published

ESLint configuration vision of ElsiKora

Downloads

1,560

Readme

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

└── ESLint-Config/
    ├── .github
    │   └── workflows
    ├── .changeset
    │   └── config.js
    ├── CHANGELOG.md
    ├── README.md
    ├── index.enums.ts
    ├── nest.js
    └── package.json

Getting Started

Installation

Install configuration package:

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

Quick Setup (CLI)

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

$ 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:

{
	"extends": "@elsikora/eslint-config"
}

For TypeScript projects:

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

For NestJS projects:

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

For React projects:

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

For JSON:

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

For Yaml:

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

Example Config

Complete .eslintrc.json example with all features:

{
	"env": {
		"es6": true,
		"jest": true,
		"node": true
	},
	"extends": ["@elsikora/eslint-config", "@elsikora/eslint-config/typescript", "@elsikora/eslint-config/nest", "@elsikora/eslint-config/react", "@elsikora/eslint-config/json", "@elsikora/eslint-config/yml"],
	"ignorePatterns": [".eslintrc.json"],
	"overrides": [
		{
			"files": ["*.ts"],
			"parser": "@typescript-eslint/parser",
			"parserOptions": {
				"ecmaVersion": "latest",
				"sourceType": "module",
				"project": "tsconfig.json",
				"tsconfigRootDir": "./"
			}
		}
	],
	"settings": {
		"import/parsers": {
			"@typescript-eslint/parser": [".ts", ".tsx"]
		},
		"import/resolver": {
			"typescript": {
				"alwaysTryTypes": true,
				"project": "./tsconfig.json"
			}
		}
	},
	"root": true
}

Project Roadmap

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

Contributing

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

  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.
    git clone https://github.com/ElsiKora/ESLint-Config.git
  3. Create a New Branch: Always work on a new branch, giving it a descriptive name.
    git 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.
    git commit -m 'Implemented new feature x.'
  6. Push to GitHub: Push the changes to your forked repository.
    git 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