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

@gossi/config-eslint

v0.13.0

Published

Add eslint to your packages. Based on [NullVoxPopuli/eslint-config](https://github.com/NullVoxPopuli/eslint-configs).

Downloads

8,455

Readme

@gossi/config-eslint

Add eslint to your packages. Based on NullVoxPopuli/eslint-config.

This lint config meta package is setup to lazily detect which plugins and configurations you have installed and automatically add them to your lint config.

This has the following benefits:

  • No need to install dependencies you don't use (typescript, for example)
  • Progressive enhancement as you decide you want more behaviors / lints
  • Minimal impact to node_modules so that local dev and C.I. are not unnecessarily hit with extra dependencies

Installation

1) Install these packages

pnpm add -D @gossi/config-eslint eslint

2) Create Config

Create a .eslintrc.js file with your desired config (see below)

3) Add scripts to execute linting

{
  "scripts": {
    "lint:js": "eslint . --cache",
    "lint:js:fix": "eslint . --fix"
  }
}

4) Add packages to describe your project

Describe your project:

  • Basic:
    • @babel/core (bring your version)
  • Javascript:
    • @babel/eslint-parser
  • Typescript:
    • @typescript-eslint/eslint-plugin
    • @typescript-eslint/parser

Zero config for these plugins, installing them is enough:

  • Ember:
    • eslint-plugin-ember
    • eslint-plugin-qunit
  • Storybook:
    • eslint-plugin-storybook

Configs

Ember

Accommodates: JS, TS, App, and Addon

// .eslintrc.js
'use strict';
const { configs } = require('@gossi/config-eslint');

// accommodates: JS, TS, App, Addon, and V2 Addon
module.exports = configs.ember();

overriding:

// .eslintrc.js
'use strict';
const { configs } = require('@gossi/config-eslint');

const config = configs.ember();

module.exports = {
  ...config,
  overrides: [
    ...config.overrides,
    // your modifications here
    // see: https://eslint.org/docs/user-guide/configuring/configuration-files#how-do-overrides-work
  ]
}

Cross Platform

This config is ESM, as ESM is the most widely supported module format across different distributions (browser, node, etc).

// .eslintrc.cjs
'use strict';

const { configs } = require('@gossi/config-eslint');

// accommodates: JS, TS, ESM, and CJS
module.exports = configs.crossPlatform();

Node

This config looks at your package.json to determine if your project is CommonJS or ES Modules.

// .eslintrc.js
'use strict';
const { configs } = require('@gossi/config-eslint');

// accommodates: JS, TS, ESM, and CJS
module.exports = configs.node();

overriding:

// .eslintrc.js
'use strict';

const { configs } = require('@gossi/config-eslint');
const config = configs.node();

module.exports = {
  ...config,
  overrides: [
    ...config.overrides,
    // your modifications here
    // see: https://eslint.org/docs/user-guide/configuring/configuration-files#how-do-overrides-work
  ]
}

Node (CJS)

This config is for when *.js is CommonJS, and ES Modules are used via the *.mjs extension.

// .eslintrc.js
'use strict';
const { configs } = require('@gossi/config-eslint');

// accommodates: JS, TS, and CJS
module.exports = configs.nodeCJS();

Node (ESM)

This config is for when *.js is ES Modules, and CommonJS are used via the *.cjs extension.

// .eslintrc.js
'use strict';
const { configs } = require('@gossi/config-eslint');

// accommodates: JS, TS, and ESM
module.exports = configs.nodeESM();

Debugging

To see what the resolved config looks like for a file

node_modules/.bin/eslint --print-config path/to/file