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

@mulekick/eslint-config-muleslint

v2.1.0

Published

Mulekicks's base JS / TS / React / Node ESLint config, following my personal standards 😁

Downloads

100

Readme

My ESLint config for Javascript, Typescript, React and Node πŸš€

GitHub package.json version GitHub License Last Commit NPM Version NPM Downloads Socket Badge

I use the ESLint extension on Visual Studio code in my day-to day coding activities. I find ESLint to be of a great help to write some proper, clean-cut ES6 code, avoid errors and enforce best practices. Here is the configuration I use to lint my *.js, *.ts, *.jsx and *.tsx files, available as a shareable config.

How I use ESLint in my dev environment

  • Windows 10 x64, Hyper-V enabled.
  • Debian Bookworm running in a Hyper-V VM.
  • Node.js v20.17.0 LTS on Debian.
  • VSCode targeting Debian through SSH.
  • ESLint v8.57.1 installed globally.
  • VSCode ESLint extension enabled.
  • @mulekick/eslint-config-muleslint included in the project's dev dependencies.
  • A minimal eslint.config.js file included in the project's root folder :
import muleslint from "@mulekick/eslint-config-muleslint";
// eslint-disable-next-line node/no-missing-import
import typescript from "typescript-eslint";

// .eslintignore doesn't work with flat configs
export default typescript.config(...muleslint, {
    ignores: [ `**/node_modules/**`, `**/dist/**`, `**/build/**` ]
});

Use it in your own project

  • Install with npx install-peerdeps --dev @mulekick/eslint-config-muleslint.
  • Be sure to add the above eslint.config.js file in your project's root folder.

Configuration details

  • This configuration uses the new eslint flat config format.
  • It extends the following configurations :

| configuration | description | | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | eslint.configs.recommended | core eslint recommended configuration | | stylistic.configs.recommended | recommended configuration for stylistic-related eslint rules | | typescript.configs.strictTypeChecked | typescript-eslint strict configuration with type-checked linting enabled πŸ€– | | react.configs.recommended | recommended configuration from the eslint react plugin | | plugin:node/recommended | recommended configuration from the eslint node plugin | | plugin:import/recommended | recommended configuration from the eslint import plugin | | plugin:security/recommended | recommended configuration from the eslint security plugin |

  • It also uses the html plugin to lint JS code in HTML pages <script> tags.
  • Quite a few of the eslint.configs.recommended and stylistic.configs.recommended options are overriden 😁
  • The use of modern ECMA features (ES6 and beyond) is enforced whenever possible.
  • The use of Crockford indentation (4 spaces) and unix-style line breaks is enforced as well.
  • ESM modules use is enforced too, therefore making strict mode mandatory everywhere πŸ‘