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

@stackonward/eslint-config

v1.0.2

Published

Shared ESLint configuration

Readme

@stackonward/eslint-config

Shared ESLint flat configs for standalone TypeScript projects and Nuxt projects. The package combines ESLint's recommended rules, typescript-eslint, and Prettier compatibility with StackOnward's baseline correctness policy.

Install

pnpm add --save-dev @stackonward/eslint-config eslint typescript

Standalone TypeScript

Create eslint.config.js:

import stackOnward from "@stackonward/eslint-config";

export default stackOnward;

Nuxt

Nuxt owns its generated base config. Compose the StackOnward policy through the generated withNuxt helper:

import stackOnwardNuxt from "@stackonward/eslint-config/nuxt";
import withNuxt from "./.nuxt/eslint.config.mjs";

export default withNuxt(...stackOnwardNuxt);

Run nuxt prepare before ESLint when .nuxt/eslint.config.mjs has not been generated yet.

Entry points

| Entry point | Purpose | | --------------------------------- | -------------------------------------------------------------------- | | @stackonward/eslint-config | Complete standalone JavaScript and TypeScript flat config | | @stackonward/eslint-config/nuxt | Policy-only flat config items composed after Nuxt's generated config |

Enforced baseline

  • Type-only imports use TypeScript's type import syntax.
  • Explicit any and unused values are errors; underscore-prefixed arguments may be unused.
  • var is forbidden, prefer-const is enabled, and equality must be strict.
  • Console output is limited to warnings and errors.
  • Generated, dependency, coverage, and build output directories are ignored by the standalone config.
  • Prettier-conflicting stylistic rules are disabled.
  • Nuxt Vue files require multiline top-level blocks and a blank line between blocks. These auto-fixable rules preserve Prettier output.

Run ESLint fixes before Prettier when formatting Vue files. This expands single-line template, script and style blocks before Prettier applies indentation.

Consumer projects can append narrower rules after this config. Keep the Nuxt export after Nuxt's generated entries so the intended policy and Prettier compatibility order is preserved.

Compatibility

  • Node.js 20.19 or newer
  • ESLint 10
  • TypeScript 5.7 through 6.0
  • ESM flat config

License

MIT