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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@gossi/config-eslint

v1.3.1

Published

Add eslint to your packages.

Readme

@gossi/config-eslint

Add eslint to your packages.

Installation

1) Install these packages

pnpm add -D @gossi/config-eslint eslint

2) Add scripts to execute linting

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

3) Create Config

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

Configs

Base

The shared common configs. It's good way to start your own config.

// eslint.config.js
import base from '@gossi/config-eslint/base';

export default configs.base(import.meta.dirname);

Node

For all node projects.

// eslint.config.js
import node from '@gossi/config-eslint/node';

export default node(import.meta.dirname);

Ember

For all ember projects.

// eslint.config.js
import ember from '@gossi/config-eslint/ember';

export default ember(import.meta.dirname);

overriding with storybook (install eslint-plugin-storybook):

import storybook from 'eslint-plugin-storybook';

import ember from '@gossi/config-eslint/ember';

export default [
  ...ember(import.meta.dirname),
  ...storybook.configs['flat/recommended'],
  ...storybook.configs['flat/csf']
];

JSON

If you wish, use it for json.

// eslint.config.js
import json from '@gossi/config-eslint/json';

export default json();

Debugging

To see what the resolved config looks like for a file

ppx @eslint/config-inspector

Utils

Some utilities to help you writing/customizing rules.

hasBabelConfig()

Find out, if a babel config is used:

import { utils } from '@gossi/config-eslint';

const usesBabelWithAConfig = utils.hasBabelConfig(import.meta.dirname);

hasTypescript()

Find out, if typescript is being used.

import { utils } from '@gossi/config-eslint';

const usesTypescript = utils.hasTypescript(import.meta.dirname);

hasTypeModule()

Find out, if package is using "type": "module".

import { utils } from '@gossi/config-eslint';

const usesESM = utils.hasTypeModule(import.meta.dirname);

hasDep()

Figure, if a given dependency is present

import { utils } from '@gossi/config-eslint';

const usesStorybook = utils.hasDep(import.meta.dirname, 'storybook');