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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@stack-lint/node

v0.0.11

Published

stack lint eslint configs for nodejs

Readme

@stack-lint/node

Node.js ESLint configuration with best practices tailored for backend and server-side JavaScript projects.
Part of the Stack Lint family — designed to be combined with @stack-lint/base and others.


📦 Installation

npm install --save-dev eslint prettier @stack-lint/base @stack-lint/node
# or
yarn add -D eslint prettier @stack-lint/base @stack-lint/node
# or
pnpm add -D eslint prettier @stack-lint/base @stack-lint/node

🚀 Usage

eslint.config.js (or eslint.config.mjs if not "type": "module"):

import getFlatConfigs from '@stack-lint/base';
import getNodeConfig from '@stack-lint/node';

export default getFlatConfigs(getNodeConfig(true)); // true if ESM, false or omit if CJS

Node + TypeScript

npm install --save-dev @stack-lint/typescript typescript
# or
yarn add -D @stack-lint/typescript typescript
# or
pnpm add -D @stack-lint/typescript typescript

eslint.config.js:

import getFlatConfigs from '@stack-lint/base';
import getNodeConfig from '@stack-lint/node';
import getTsConfigs from '@stack-lint/typescript';

export default getFlatConfigs(
  getNodeConfig(true), // true if ESM, false or omit if CJS
  ...getTsConfigs({
    tsconfigRootDir: import.meta.dirname,
    // tsRootDir: 'src/' your tsconfigs files rootDir, if * then no need the field
  }),
);

Explanation

  • getNodeConfig(true || { extension: true }) returns the Node.js ESLint configuration optimized for ESM (ECMAScript Modules) environments.
  • Passing true enables ESM-specific rules and settings; pass false or omit the argument for CommonJS environments.
  • Passing { extension: true } enables ESM-specific rules and settings and extension: true for omit extension check if you use bundler for resolve extension
  • getFlatConfigs(...) takes one or more ESLint config objects and merges them into a single flat configuration that ESLint can directly use.