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

eslint-config-rakeshshrestha

v3.0.3

Published

Personal ESlint preference for better tooling

Downloads

34

Readme

eslint-config-rakeshshrestha

Eslint preference rules

  • Note This is my personal preference configs which I learnt & found helpful along the way. I can assure your that using my eslint config you'll find yourself at better code practices & easily save yourself from mistakes.

Installation

  • Using yarn add eslint-config-rakeshshrestha -D
  • Using npm install eslint-config-rakeshshrestha -D
  • Install eslint by yarn add eslint -D or npm install eslint -D. Don't forget to install the eslint plugin in your text editor. Note create-react-app has eslint installed by default inside of react-scripts. So, installing new version of eslint will bring unwanted hard to detect problem so skip this step on create-react-app project.
  • Then, install @babel/core & @babel/eslint-parser on dev flag.
  • Restart your eslint server or you can also restart your whole terminal.

Usage

  • Create a file on your root dir named .eslint.rc. It can be .json or .js as well.
  • If you simple want the javascript setup.
{
  "extends": "rakeshshrestha"
}
  • That's it.

Advanced Usage

  • There are other available configs example react, typescript, import-order, node, nextjs.
  • Currently, only react & typescript is available.

Debugging

It's pretty simple. Go your output tab on text editor it will throw some errors and you'll find the problems with eslint. Another thing you can also do is run npx eslint . if it runs then perfect if it doesn't follow the error messages. Every time you add some eslint plugins or make changes to eslintrc file; restart your eslint server.

Possible Errors

  • If you get react/no-unstable-nested-components was not found then install eslint-plugin-react
  • If you get import/no-* was not found then install eslint-plugin-import

React & typescript

  • Typescript is by default enabled for all configs.
{
  "extends": "rakeshshrestha/react"
}

Suggestion

  • You can mix up these configs to get better insights. Here is one which I highly suggest you to do
{
  "extends": ["rakeshshrestha", "rakeshshrestha/react"]
}

For Nextjs

  • Please use this for optimum eslint errors and warnings.
{
  "extends": ["rakeshshrestha", "rakeshshrestha/react", "next/core-web-vitals"]
}