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

@we-are-singular/eslint-config

v1.4.0

Published

singular eslint stuff

Downloads

98

Readme

@we-are-singular/eslint-config

npm version

This package provides a shared ESLint configuration for Singular projects.

Installation

npm install --save-dev @we-are-singular/eslint-config

Usage

config()

This function is used to create an ESLint configuration object. it just deeply merges the provided arguments.

extend()

This function is used to create an ESLint configuration object. it extends the presets.all configuration and merge the provided arguments.

presets

list of presets that can be used to create an ESLint configuration object.

overrides

list of override factories that can be used to create an ESLint overwrite rule.

Example

// .eslintrc.js

const { config, overrides, presets } = require("@we-are-singular/eslint-config")

module.exports = config(
  // some presets
  presets.react,
  presets.typescript,
  // your rules
  {
    rules: {
      "no-console": "warn",
    },
    overrides: [
      // some overrides
      overrides.vitestNode(["apps/backend", "packages/logger"]),

      // your rules
      {
        files: ["*.test.ts", "*.test.tsx"],
        rules: {
          "no-console": "off",
        },
      },
    ],
  }
)

Example using extend()

// .eslintrc.js

const { extend, overrides } = require("@we-are-singular/eslint-config")

module.exports = extend({
  rules: {
    "no-console": "warn",
  },
  overrides: [
    // some overrides
    overrides.vitestNode(["apps/backend", "packages/logger"]),

    // your rules
    {
      files: ["*.test.ts", "*.test.tsx"],
      rules: {
        "no-console": "off",
      },
    },
  ],
})

Example as ESLint preset

// .eslintrc.js

/** @type {import("eslint").Linter.Config} */
module.exports = {
  root: true,
  extends: ["@we-are-singular/eslint-config/all"],
  overrides: [
    // your rules
    {
      files: ["*.test.ts", "*.test.tsx"],
      rules: {
        "no-console": "off",
      },
    },
  ],
}

Releasing a new version

To release a new version, you need to have access to the @we-are-singular npm organization.

  1. Make sure you are logged in to the @we-are-singular npm organization by running npm login and following the instructions.
  2. Run npm run release to trigger the release process.
  3. Follow the instructions and make sure to select the correct version type.
  4. The release will be published to npm and github automatically.