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

@theurgi/eslint-config

v1.13.0

Published

A dynamic multi-framework ESLint config.

Downloads

19

Readme

eslint-config

A dynamic multi-framework ESLint config.

Features

Supported frameworks/tools

The lint rules that are applied to a given file depend on its extension and whether its associated package is a dependency of your project.

Examples

  1. A file with a .tsx extension inside of a project with dependencies on typescript, react, and prettier will be linted with rules for TypeScript, React, and Prettier; but not with rules for Svelte or Vue.
  2. A file whose name matches the glob **/*.{spec,test}.{js?(x),ts?(x)} inside of a project with a dependency on jest will be linted with Jest rules.

Node.js

Node.js projects are a special case because node itself is not typically installed as a project level dependency and it does not always use unique file extensions. To address this, this package exports a separate config with additional rules for Node.js. See Usage.

Internally extended configurations

In addition to framework or file specific lint rules, rules common to multiple file types are internally extended from the following configs/plugins:

Install

Install as a devDependency with your preferred Node.js package manager (npm, pnpm, yarn, etc.):

pnpm i -D @theurgi/eslint-config

Usage

Extend this package in your local eslint config (e.g. .eslintrc.json):

For non Node.js projects:

{
  "extends": ["@theurgi/eslint-config"]
}

For Node.js projects:

This config includes all the non-Node rules plus Node specific rules and overrides.

{
  "extends": ["@theurgi/eslint-config/node"]
}

Editor support

VSCode

For error highlighting and auto-fix-on-save, install the ESLint extension and configure VSCode's settings as follows:

{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": true
  },

  "eslint.validate": [
    "astro",
    "javascript",
    "javascriptreact",
    "json",
    "json5",
    "jsonc",
    "svelte",
    "typescript",
    "typescriptreact",
    "vue"
  ]
}

Thanks 🙏

Special thanks to privatenumber whose eslint-config was the primary reference for this package.