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

@shaizei/eslint-config

v0.1.0-beta.13

Published

This package contains shareable ESLint configuration used by the applications created with @shaizei/cli.

Downloads

14

Readme

Getting Started

1. Installation

Using Yarn:

  yarn add @shaizei/eslint-config --dev

Using npm:

  npm install @shaizei/eslint-config --save-dev

2. Usage

  • Create a new file and name it as .eslintrc.js
  • Import relevant config file from @shaizei/eslint-config and just export it as follows.

For JavaScript projects:

module.exports = {
  extends: '@shaizei/eslint-config/javascriptReact',
};

For TypeScript projects:

module.exports = {
  extends: '@shaizei/eslint-config/typescriptReact',
};
  • In order to have a .eslintignore file as well, just run the following command from terminal:
  cat ./node_modules/@shaizei/eslint-config/.eslintignore >> .eslintignore

Override Default Config

If you want to override the default configuration, then add the following code in .eslintrc.js file:

For JavaScript projects:

module.exports = {
  extends: '@shaizei/eslint-config/javascriptReact',
  // your config options goes here, e.g. plugins: [...]
};

For TypeScript projects:

module.exports = {
  extends: '@shaizei/eslint-config/typescriptReact',
  // your config options goes here, e.g. plugins: [...]
};

VSCode ESLint Extension Setup

As we're not installing ESLint locally per project, but leveraging ESLint and associated packages installed in @shaizei/eslint-config project. Thus, we need to inform VSCode ESLint extension that how to resolve ESLint.

  • Go to settings.json in VSCode.

  • Add following settings:

  "eslint.nodePath": "./node_modules/@shaizei/eslint-config/node_modules"

Above mentioned settings will let the extension read ESLint from @shaizei/eslint-config.

Also, for TypeScript, we need to tell ESLint extension to lint .ts and .tsx files as well. We recommend to add following setting as well in settings.json:

  "eslint.validate": [
    "javascript",
    "javascriptreact",
    "typescript",
    "typescriptreact"
  ],