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

ember-eslint

v0.6.1

Published

The all in one ESLint configuration for ember projects

Readme

ember-eslint

The easiest way to get linting going in in your ember project

Setup

install from npm:

npm add ember-eslint eslint

or, from source (by editing your package.json):

"devDependencies": {
  "ember-eslint": "github:NullVoxPopuli/ember-eslint"
}

In eslint.config.mjs,

import { ember } from 'ember-eslint';

export default [
    ...ember.recommended(import.meta.dirname),
];

In package.json:

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

And that's it!

The configs

All configs will "do the right thing" when they detect that you're using (or not using) TypeScript, V2 (Vite) projects, etc

recommended aka "official"

This config mirrors the lint config that is specified in ember-cli, and where any significant change has a Request For Comments.

import { ember } from 'ember-eslint';

export default [
    ...ember.recommended(import.meta.dirname),
];

Support Matrix

This config supports a 2x2x2 matrix of features:

  • TypeScript vs JavaScript
  • App vs Addon
  • type=module packages and classic packages

Exported utilities

  • utils.hasBabelConfig - returns true when the host environment has a babel config
  • utils.hasTypescript - returns true when the host environment has typescript
  • utils.hasTypeModule - returns true when the host environment has type=module in the package.json
  • parsers.esm - the parser options for JS (babel) and TS ESM files

Debugging ESLint

Docs: https://eslint.org/docs/latest/use/configure/debug

Print a file's calculated configuration

npx eslint --print-config path/to/file.js

Inspecting the config

npx eslint --inspect-config