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

@rasmuslp/eslint-config

v10.1.1

Published

My configs

Readme

@rasmuslp/eslint-config

NPM package GitHub: CI

Installation

Install the config:

npm install --save-dev @rasmuslp/eslint-config

Usage

Configure eslint in your project by using this configuration in your local eslint.config.js (or eslint.config.ts — the package ships TypeScript declarations).

// eslint.config.js
import { defineConfig } from 'eslint/config';
import rasmuslpConfig from '@rasmuslp/eslint-config';

export default defineConfig([rasmuslpConfig]);

Options

The default export is the config with no optional integrations enabled. For Node or Jest support, use the named eslintConfigRasmuslp factory instead. It is async, so await it:

// eslint.config.js
import { defineConfig } from 'eslint/config';
import { eslintConfigRasmuslp } from '@rasmuslp/eslint-config';

export default defineConfig([await eslintConfigRasmuslp({ withJest: true, withNode: true })]);

| Option | Default | Effect | | ---------- | ------- | ------------------------------------------------------------------------------------ | | withNode | false | Enables eslint-plugin-n (Node.js rules). Requires installing eslint-plugin-n. | | withJest | false | Enables eslint-plugin-jest (Jest rules). Requires installing eslint-plugin-jest. |

Both plugins are optional peer dependencies — install the corresponding package only when you enable its option:

npm install --save-dev eslint-plugin-n      # for withNode
npm install --save-dev eslint-plugin-jest   # for withJest

Lastly, specify the minimum supported Node version in package.json to enable checks for using unsupported Node features.

	"engines": {
		"node": ">=22.13.0"
	}

Behaviour

Root-level JS files

Typed linting is disabled for all root-level JS files (*.js, *.mjs, *.cjs). This is intentional: the assumption is that your actual source lives in a subfolder (e.g. src/), so the files left at the root are config files such as eslint.config.js or .ncurc.js. These typically live outside the TypeScript project, so applying type-aware rules to them would otherwise error.

Files in subdirectories are unaffected and keep typed linting. If you keep source files at the repository root, they will not get typed linting — move them into a subfolder to opt back in.