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

@nake/eslint-config

v1.3.1

Published

Eslint shareable config for your nake apps

Downloads

18

Readme

@nake/eslint-config

Eslint shareable config for your nake apps

This ESLint config is extended from both airbnb and prettier styles. It uses eslint-plugin-compat plugin for browser compatibility linter. It provides six extend options for different environment.

Installation

# Install with npx
$ npx install-peerdeps --dev @nake/eslint-config

# Install with yarn
$ yarn add --dev @nake/eslint-config
$ yarn add --dev prettier eslint babel-eslint
$ yarn add --dev eslint-plugin-import eslint-plugin-jsx-a11y eslint-plugin-react

Use npx to install peerdeps automatically or install peerDependencies with npm/yarn manually.

Usage

After installation, add following contents to your .eslintrc.json or the eslintConfig entry of package.json file.

Default

For react project.

{
  "extends": ["@nake"]
}

ES2015+ Base

For vanilla javascript project with no framework.

{
  "extends": ["@nake/eslint-config/base"]
}

React

For react project, the same as default config.

{
  "extends": ["@nake/eslint-config/react"]
}

Wxapp (微信小程序)

For wechat miniProgram project.

{
  "extends": ["@nake/eslint-config/wxapp"]
}

This environment can't support browser compatibility linter

Node

For Node.js project.

{
  "extends": ["@nake/eslint-config/node"]
}

It recommends a use of the "engines" field of package.json. The "engines" field is used by node/no-unsupported-features/* rules.

This environment can't support browser compatibility linter

With Webpack

For project built with webpack, if you are using resolver.alias feature, eslint can't lint import path correctly, you should extends webpack settings.

{
  "extends": ["@nake", "@nake/eslint-config/webpack"]
}

With babel-plugin-module-resolver

If you use babel-plugin-module-resolver to setup a custom alias for directories, specific files, or even other npm modules, you should extends babel settings.

{
  "extends": ["@nake", "@nake/eslint-config/babel"]
}

With Jest

For react or base web project with jest testing framework.

{
  "extends": ["@nake", "@nake/eslint-config/jest"]
}

Browser compatibility linter

First, add browsers that we support in your package.json or config file that browserslist supports.

{
  "browserslist": [
    "defaults",
    "> 0.5%",
    "last 2 versions",
    "Firefox ESR",
    "not ie <= 9",
    "not op_mini all"
  ]
}

Second, ESLint will linter your code with predefined browserslist automatically. It will shot an error message to tell you which feature have not be well supported by these browsers (e.g. fetch and promises):

Finally, after install these polyfills, we should add them to whitelist to prevent ESLint shotting error message again.

yarn add whatwg-fetch es6-promise
{
  "extends": ["@nake"],
  "settings": {
    "polyfills": ["fetch", "promises"]
  }
}

eslintConfig in package.json

I like moving .eslintrc.json and .eslintignore file from project root to package.json, this makes my project cleaner. If you want to respect .gitignore as eslintIgnore, make your eslint script with --ignore-path .gitignore is a good idea.

{
  "scripts": {
    "eslint": "eslint src --ext .js; exit 0",
    "eslint:fix": "eslint src --ext .js --fix; exit 0"
  },
  "eslintConfig": {
    "extends": ["@nake"],
    "settings": {
      "polyfills": ["fetch", "promises"]
    }
  }
}

Work with VS Code

Share my VS Code settings for ESLint with autoFixOnSave feature.

{
  "editor.formatOnSave": true,

  // ESlint
  "eslint.packageManager": "yarn",
  "eslint.alwaysShowStatus": true,
  "eslint.autoFixOnSave": true,
  "eslint.validate": [
    "javascript",
    "javascriptreact",
    { "language": "vue", "autoFix": true },
    { "language": "wxs", "autoFix": true }
  ]

  // Prettier
  "prettier.eslintIntegration": true,
}

Configure the path mapping in jsconfig.json, e.g.:

{
  "compilerOptions": {
    "emitDecoratorMetadata": true,
    "experimentalDecorators": true,
    "baseUrl": ".",
    "paths": {
      "@/*": ["./src/*"]
    }
  }
}

Bonus

Extend

You can override any rules with your own prefs.

License

MIT