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

@pedroaal/eslint-config

v1.0.6

Published

The shared eslint configuration for personal projects.

Downloads

2

Readme

This is a base configuration for linting personal projects.

Installation and use

Install eslint and @pedroaal/eslint-config:

npm i -D eslint @pedroaal/eslint-config

Generate a file .eslintrc.cjs with the following content:

module.exports = {
   root: true,
   extends: [
     '@pedroaal'
   ],
}

Extend the rules

To use the extended rules they must be declared in the eslint configuration file: .eslintrc.cjs.

Frameworks support, one for ReactJS, NextJS and NestJS, SoliJS. Test env support, Jest, Vitest.

You should always import the general rules first and then the extended ones, since the latter overwrite some general rules.

Extend react rules

To correctly use the general rules of eslint and react, it must be imported as follows in the same order presented:

module.exports = {
   root: true,
   extends: [
     '@pedroaal', '@pedroaal/eslint-config/react'
   ]
}

Extend nest rules

To correctly use the general rules of eslint and nest, it must be imported as follows in the same order presented:

module.exports = {
   root: true,
   extends: [
     '@pedroaal', '@pedroaal/eslint-config/nest'
   ]
}

Extend next rules

To use the rules correctly, they must be extended from the general rules, react and next. In this same order.

module.exports = {
   root: true,
   extends: [
     '@pedroaal', '@pedroaal/eslint-config/react', '@pedroaal/eslint-config/next'
   ]
}

Extend solid rules

To use the rules correctly, they must be extended from the general rules, react and next. In this same order.

module.exports = {
   root: true,
   extends: [
     '@pedroaal', '@pedroaal/eslint-config/solid'
   ]
}

Extend jest rules

To use the rules correctly, they must be extended from the general rules, react and next. In this same order.

module.exports = {
   root: true,
   extends: [
     '@pedroaal', '@pedroaal/eslint-config/jest'
   ]
}

Extend vitest rules

To use the rules correctly, they must be extended from the general rules, react and next. In this same order.

module.exports = {
   root: true,
   extends: [
     '@pedroaal', '@pedroaal/eslint-config/vitest'
   ]
}

Note: the .cjs extension allows you to tell node that it has to import this file as a CommonJS module and not as an ES Module. See this issue.