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

@danielgiljam/eslint-config

v3.0.3

Published

The ESLint config I use.

Downloads

10

Readme

@danielgiljam/eslint-config

The ESLint config I use.

How To Use

Install @danielgiljam/eslint-config and its peer dependencies.

npm i @danielgiljam/eslint-config @typescript-eslint/eslint-plugin@^4.0.1 @typescript-eslint/parser@^4.0.0 eslint@^7.12.1 eslint-config-prettier@^8.3.0 eslint-config-standard-jsx@^10.0.0 eslint-config-standard-with-typescript@^21.0.1 eslint-plugin-import@^2.25.4 eslint-plugin-node@^11.1.0 eslint-plugin-promise@^5.0.0 eslint-plugin-react@^7.28.0 typescript@^4.5.5

Create a file called .eslintrc.js.

touch .eslintrc.js

Export an ESLint config from .eslintrc.js that extends @danielgiljam/eslint-config.

module.exports = {extends: "@danielgiljam"}

Recommended Setup

The recommended way to use @danielgiljam/eslint-config is together with @danielgiljam/prettierrc and Prettier.

ESLint catches/fixes potential bugs and problems and Prettier reprints the code to ensure the format is right and the style is consistent.

You can implement these tools into your development workflow however you like. However, my personal favorite ways of implementing them are the following:

Fix and Format Code In Place With An NPM script

  1. Modify your package.json to include the following NPM scripts:
    {
      "scripts": {
        "fix": "eslint --fix .",
        "format": "prettier --write .",
        "ff": "npm run fix && npm run format"
      }
    }
  2. Typing npm run ff in your terminal then applies @danielgiljam/eslint-config and @danielgiljam/prettierrc to your source code.

Fix and Format On Save in Visual Studio Code

  1. Install the following extensions:
  2. Make the following changes to your settings:
    {
      "editor.defaultFormatter": "esbenp.prettier-vscode",
      "editor.formatOnSave": false,
      "editor.codeActionsOnSave": [
        "source.fixAll.eslint",
        "source.fixAll.format"
      ]
    }
  3. Now when you save a file, it will first be fixed and then formatted in place.

Version History

View changelog.