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

@lunit/eslint-config

v1.0.0

Published

Lunit ESLnt Config

Downloads

200

Readme

@lunit/eslint-config

A TypeScript ESLint ruleset designed for lunit projects based on @rushstack/eslint-config.

Installation

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

Usage

Referring to the sapmple-project folder, create eslint-config folder in the project repository root folder, add index.js file, and then extend the eslint-config folder to the .eslintrc.cjs file.

# Project folder structure
sample-project/
├── .eslintrc.cjs
└── eslint-config
    ├── index.js
    └── mixins
        └── react.js
// .eslintrc.cjs
module.exports = {
  ...
  extends: [
    './eslint-config', // Extend common ESLint config
  ],
  settings: {
    react: {
      // Specifies the current React version (e.g. version: '18.2')
      // If not specified (default 'detect'), the entire React library will be loaded,
      // which may slow down the linting process.
      version: 'detect',
    },
  },
  ...
};

If necessary, add your own mixin to the eslint-config/mixins folder and use it, or use the mixins in @rushstack/eslint-config/mixins. (Refer to eslint-config/index.js)

// eslint-config/index.js
module.exports = {
  ...
  extends: [
    // (required) Extend the @lunit/eslint-config.
    // (@rushstack/eslint-config/profile/web-app is included by default.)
    '@lunit/eslint-config',
    // React mixin provided by rushstack (requires installation of @rushstack/eslint-config package)
    // '@rushstack/eslint-config/mixins/react',
    // You can create and use your own mixin as follows.
    './mixins/react',
  ],
  ...
};

Refer to the default settings in @lunit/eslint-config/index.js & @rushstack/eslint-config/profile/web-app and add your own rules to the config if necessary. Any esconfig rule entries added must have a valid RATIONALE.

rules: {
  ...
  // RATIONALE : Enforce consistent function types for function components.
  'react/function-component-definition': 'error',
  ...
},