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

eslint-config-shiny

v3.1.0

Published

An eslint config that makes your code so clean and polished that it shines!

Downloads

252

Readme

eslint-config-shiny

NPM license NPM version NPM downloads

Make your code so clean and polished that it shines! :sparkles:

eslint-config-shiny is a sophisticated configuration tool to create the most optimal eslint experience by doing all the heavy work for you! Just say what framework and for what purpose you want to use it and eslint-config-shiny will do the rest for you.

As of now, it does not work with eslint 9 as most plugins haven't updated yet. Please stay with eslint 8.57.0!

Installation

pnpm i -D eslint-config-shiny

Create an empty eslint.config.js, if you have "type": "module" specified in your package.json or eslint.config.mjs if not.

import shiny from 'eslint-config-shiny'

export default await shiny()

In use with other frameworks:

import shiny from 'eslint-config-shiny'

export default await shiny({ configs: ['react', 'vitest'] })

With own plugins (legacy):

import shiny from 'eslint-config-shiny'
import unicorn from 'eslint-plugin-unicorn'


export [
    ...await shiny({ configs: ['react'] }),
    {
        rules: {
            ...unicorn.configs.recommended.rules
        }
    }
]

With own plugins (modern):

import shiny from 'eslint-config-shiny'
import prettier from 'eslint-config-prettier'

export [
    ...await shiny({ configs: ['react'] }),
    ...prettier
]

Important :warning:

  • It's forced to be ESM
  • It's designed to be used with TypeScript specifically
  • It uses the modern flat config
  • It installs a lot of eslint plugins
  • It's written to output performant code. Any plugins that increase readability, but can decrease the performance in any away, will be deactivated.

Supported frameworks

[x] Angular

[x] Cypress

[x] Jest

[x] Node.js

[x] React

[x] Storybook

[x] TestingLibrary

[x] Vitest

[x] Vue

Supported File Formats

[x] JSON

[x] TypeScript

Options :sparkles:

Configuration

If you have further questions with the config object, you can use the type ShinyConfig

cache

  • Caches the fully converted config array under cwd/.temp/shiny-config.json
  • If enabled, it will always prioritize the cached config and won't patch or transform anything, except from previously used renames.
  • All plugins, parsers and processors need to be imported, so it only skips the converting importing time.
  • default: true

configs

  • Specify which configuration preset you want to use
  • The preset names are mapped to the profile file names.
  • Possible profiles:
    • angular
    • base
    • cypress
    • format
    • fp
    • jest
    • json
    • node
    • react
    • test-angular
    • test-base
    • test-react
    • test-vue
    • test-web
    • tsdoc
    • vitest
    • vue
    • web
  • Default: ['base']
  • Profiles extend from each other in a tree structure way. You are still allowed to use as many profiles as you want.

ignoreFiles

  • Specifies the ignore files you want to use
  • Default: ['.gitignore', '.eslintignore']

indent

  • Enables all indentation rules, i.e. : @stylistic/ts/indent, vue/html-indent and @stylistic/jsx/jsx-indent
  • It requires a valid .prettierc file to work
  • default: false

patchVSCode

  • Specifies if you want to patch VSCode to optimize the native linting experience
  • Default: true

prettier

  • Specifies if eslint-config-shiny should look into your prettier config to add stylistic rules
  • Default: true

rename

  • renames used plugins.
  • Default values will always be renamed
  • default:
{
    '@arthurgeron/react-usememo': 'use-memo',
    '@typescript-eslint': 'ts',
    '@microsoft/sdl': 'sdl'
}

root

  • Specifies the root directory
  • All plugins fetch the corresponding files from the given root directory and will ignore sub directory files
  • default: process.cwd()

© Torathion 2024