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

@danieldanielsson/eslint-config

v1.2.2

Published

[![GitHub last commit](https://img.shields.io/github/last-commit/danieldanielsson/dotfiles)](https://github.com/DanielDanielsson/eslint-config-danieldanielsson) [![npm version](https://badge.fury.io/js/@danieldanielsson%2Feslint-config.svg)](https://badge

Downloads

24

Readme

GitHub last commit npm version

Eslint config - Daniel Danielsson

This is how I configure eslint and prettier in my projects! It works as a good base for anyones eslint and prettier, since any rule is configurable to personal prefrences (See Customization).

Installation

  1. First, install the package and make sure it's added to your package.json file in the devDependencies.
npm i -D @danieldanielsson/eslint-config
  1. We need to put our eslint settings in a file in the root of your project. Create a .eslintrc or .eslintrc.js file for that:
{
  "extends": ["@danieldanielsson/eslint-config"]
}

TypeScript users will also need a tsconfig.json file in their project. An empty object ({}) will do!

  1. And let's add two scripts to our package.json to lint and fix lint errors:
"scripts": {
  "lint": "eslint .",
  "lint:fix": "eslint . --fix"
},

Now you can manually lint your code by running npm run lint and fix all fixable issues with npm run lint:fix. We'll look into how this can be automated on save in VSCode in just a bit, but since everyone working on your project might not have this configured it's great to have these scripts!

Customization

If you'd like to overwrite eslint or prettier settings, you can add the rules in your .eslintrc file. The ESLint rules go directly under "rules".

{
  "extends": [
    "@danieldanielsson/eslint-config"
  ],
  "rules": {
    "no-console": 2,
  }
}

Prettier Rules

If you want custom prettier options, it's recommended to create a .prettierrc file in your root directory like so:

{
  "singleQuote": true,
  "endOfLine": "auto",
  "tabWidth": 2
}

VSCode

Once you have done the above installs, I recommend you to configure VSCode to lint and fix for you. Here's hpw I do it:

  1. Install the ESLint package
  2. Now we need to setup some VSCode settings via Code/FilePreferencesSettings. It's easier to enter these settings while editing the settings.json file, so click the Open (Open Settings) icon in the top right corner:

 "eslint.validate": [
    "javascript",
    "javascriptreact",
    "typescript",
    "typescriptreact"
  ],
  "eslint.format.enable": true,
  "eslint.workingDirectories": [],
  "eslint.runtime": "",
  "eslint.debug": true,

// These are all my auto-save configs
"editor.formatOnSave": true,
// turn it off for JS, JSX, TS and TSX , we will do this via eslint instead.
"[javascript][javascriptreact][typescript][typescriptreact]": {
  "editor.formatOnSave": false
},
// tell the ESLint plugin to run on save
"editor.codeActionsOnSave": {
  "source.fixAll.eslint": true
},

After attempting to lint your file for the first time, you may need to click on 'ESLint' in the bottom right and select 'Allow Everywhere' in the alert window.

Finally you'll usually need to restart VSCode.