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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@krauters/eslint-config

v1.4.0

Published

TypeScript linting configuration.

Downloads

233

Readme

License visitors

Version npm version GitHub Stars Forks

GitHub Issues Open PRs Commits per Month Contributors Last Commit

install size Code Size Repo Size

ESLint Config

This configuration integrates ESLint and TypeScript ESLint, built to ensure clean, consistent, and maintainable code in JavaScript and TypeScript projects.

Tenets

  1. Feedback Loops: In DevOps, feedback loops are essential. Realtime linting gives developers instant insight, allowing faster fixes and smoother workflows. So, configure your IDE to provide linting feedback as you type.

  2. Code Consistency: Linting ensures uniform coding standards across the team, reducing errors and enhancing collaboration by maintaining clarity and readability.

Rules

All linting rules are defined in rules.js. This configuration offers a strong foundation suitable for most projects, promoting code quality from the start while remaining flexible for customization.

Usage

Commands You Need

# Check if your code passes lint rules
npm run lint

# Fix what can be auto-fixed
npm run fix

Using this Lint Config in Your Project

  1. Install the necessary dependencies:
npm install @krauters/eslint-config --save-dev
  1. Add a config file eslint.config.js to the root of your project with the following contents,

ESM

// eslint.config.js

import eslintConfig from '@krauters/eslint-config'

export default eslintConfig

CommonJS

// eslint.config.js

const eslintConfig = require('@krauters/eslint-config')

module.exports = eslintConfig
  1. Add these npm scripts to your package.json,
{
  ...
  "scripts": {
    "test": "npm run lint",
    "lint": "npx eslint src/**",
    "fix": "npm run lint -- --fix"
  }
}
  1. Update your README to show off your linting setup,
## Lint
This package uses [@krauters/eslint-config](https://github.com/krauters/eslint-config).

```zsh
# Check if your code follows the rules
npm run lint

# Fix what can be auto-fixed
npm run fix
```
  1. Now, let’s try it out.
npm run lint
npm run fix

Development

Testing Locally

Want to test this linting config locally between two repos? Easy.

  • Repo1 is the ESLint config repo.
  • Repo2 is a JS/TS project using Repo1.

Steps

  1. Clone both repos.
  2. Link 'em up. From the root of Repo1, run:
npm link
  1. Then in Repo2, do this:
npm link @krauters/eslint-config
  1. When you’re done testing, unlink it with,
npm unlink @krauters/eslint-config

Resources

Contributing

The goal of this project is to continually evolve and improve its core features, making it more efficient and easier to use. Development happens openly here on GitHub, and we’re thankful to the community for contributing bug fixes, enhancements, and fresh ideas. Whether you're fixing a small bug or suggesting a major improvement, your input is invaluable.

License

This project is licensed under the ISC License. Please see the LICENSE file for more details.

🥂 Thanks Contributors

Thanks for spending time on this project.