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-community/eslint-plugin-mysticatea

v15.6.0

Published

Additional ESLint rules.

Downloads

1,909

Readme

@eslint-community/eslint-plugin-mysticatea

npm version Downloads/month Build Status codecov Dependency Status

Additional ESLint rules and ESLint configurations for @mysticatea.

💿 Installation

npm install --save-dev eslint @eslint-community/eslint-plugin-mysticatea

Requirements

  • Node.js ^12.22.0 || ^14.17.0 || >=16.0.0 or newer versions.
  • ESLint ^6.6.0 || ^7.0.0 || ^8.0.0 or newer versions.

📖 Usage

Write in your ESLint configurations: http://eslint.org/docs/user-guide/configuring#using-the-configuration-from-a-plugin

Configs

  • plugin:@eslint-community/mysticatea/es2022 ... Basic configuration for ES2022.
  • plugin:@eslint-community/mysticatea/es2021 ... Basic configuration for ES2021.
  • plugin:@eslint-community/mysticatea/es2020 ... Basic configuration for ES2020.
  • plugin:@eslint-community/mysticatea/es2019 ... Basic configuration for ES2019.
  • plugin:@eslint-community/mysticatea/es2018 ... Basic configuration for ES2018.
  • plugin:@eslint-community/mysticatea/es2017 ... Basic configuration for ES2017.
  • plugin:@eslint-community/mysticatea/es2016 ... Basic configuration for ES2016.
  • plugin:@eslint-community/mysticatea/es2015 ... Basic configuration for ES2015.
  • plugin:@eslint-community/mysticatea/es5 ... Basic configuration for ES5.
  • plugin:@eslint-community/mysticatea/+modules ... Additional configuration for ES modules.
  • plugin:@eslint-community/mysticatea/+browser ... Additional configuration for browser environment.
  • plugin:@eslint-community/mysticatea/+node ... Additional configuration for Node.js environment.
  • plugin:@eslint-community/mysticatea/+eslint-plugin ... Additional configuration for ESLint plugins. This includes plugin:@eslint-community/mysticatea/+node setting.

Details

The main configurations plugin:@eslint-community/mysticatea/es* does:

  • detect bug-like code by ESLint rules.
  • enforce whitespace style by Prettier.
  • handle the .ts files as TypeScript then check by typescript-eslint-parser and eslint-plugin-typescript.
  • handle the .vue files as Vue.js SFC then check by vue-eslint-parser and eslint-plugin-vue.
  • handle the files in test/tests directory as mocha's test code.
  • handle the files in scripts directory as Node.js environment.
  • handle the .eslintrc.js file as a Node.js script.
  • handle the webpack.config.js file as a Node.js script.
  • handle the rollup.config.js file as an ES module.

You can use combination of a main configuration and some additional configurations. For examples:

For Node.js
{
    "extends": [
        "plugin:@eslint-community/mysticatea/es2015",
        "plugin:@eslint-community/mysticatea/+node"
    ]
}

It handles .js files as scripts and .mjs files as modules.

For Browsers
{
    "extends": [
        "plugin:@eslint-community/mysticatea/es2015",
        "plugin:@eslint-community/mysticatea/+browser"
    ]
}
For Browsers with ES modules
{
    "extends": [
        "plugin:@eslint-community/mysticatea/es2015",
        "plugin:@eslint-community/mysticatea/+modules",
        "plugin:@eslint-community/mysticatea/+browser"
    ]
}
For ESLint plugins
{
    "extends": [
        "plugin:@eslint-community/mysticatea/es2015",
        "plugin:@eslint-community/mysticatea/+eslint-plugin"
    ]
}

Rules

This plugin has some original rules and foreign rules.

Original rules

Foreign rules

Q: Why don't you use those plugins directly? > A: The combination with shareable configs and plugins has some problems because shareable configs were not designed to be used with plugins. @nzakas illustrated a way to use plugins as shareable configs together with other plugins in the discussion eslint/eslint#3458. This is the way.

🚥 Semantic Versioning Policy

This plugin follows semantic versioning and ESLint's Semantic Versioning Policy.

📰 Changelog

❤️ Contributing

Welcome contributing!

Please use GitHub's Issues/PRs.

Development Tools

  • npm test runs tests and measures coverage.
  • npm run clean removes the coverage result of npm test command.
  • npm run coverage shows the coverage result of npm test command.
  • npm run update updates auto-generated files.
  • npm run watch runs tests and measures coverage when source code are changed.