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

@sometic/eslint-config

v1.0.7

Published

Shared ESLint configuration for the Sometic monorepo.

Readme

@sometic/eslint-config

Shared ESLint flat config for Sometic TypeScript packages.

@sometic/eslint-config is the lint baseline used across the Sometic monorepo. It exports createPackageConfig(options?), which builds an ESLint 9 flat config from @eslint/js recommended rules, typescript-eslint recommended configs, and a custom sometic/no-implementation-comments rule. Package authors and consumers who want the same strictness can reuse it outside the monorepo.

Sometic coding standards ban implementation comments, forbid any, prefer type-only imports, and reject TODO/FIXME noise in source. Encoding those rules in a publishable config keeps adapters, engines, and apps aligned without copying ESLint fragments package by package. The config ignores build outputs (dist, coverage, .turbo) and common tooling files so lint stays focused on product TypeScript.

Standout behavior: createPackageConfig accepts optional tsconfigRootDir for typed lint via projectService; enables @typescript-eslint/consistent-type-imports with separate type imports; errors on @typescript-eslint/no-explicit-any and unused vars (with _ ignore patterns); turns on no-warning-comments for todo/fixme/xxx/hack; and applies sometic/no-implementation-comments to TypeScript while disabling that rule for plain JS config files. The custom rule allows license headers and required tooling directives only.

This package is developer tooling, not a runtime adapter. It sits beside TypeScript and ESLint peers, while application behavior remains in packages rooted at @sometic/core. Product overview: Introduction. Architecture and standards live under the docs site at https://sometic.dev/.

Use it when you maintain Sometic packages or want the same comment and TypeScript discipline in a consumer monorepo. Skip it when you already have a house ESLint stack and do not want the no-implementation-comments policy. It does not replace framework adapters, CLI scaffolding, or UI engines.

Install

Peers: eslint ^9, typescript ^5.

pnpm add -D @sometic/eslint-config eslint typescript
npm install -D @sometic/eslint-config eslint typescript
yarn add -D @sometic/eslint-config eslint typescript

Usage

import { createPackageConfig } from "@sometic/eslint-config";

export default createPackageConfig({
    tsconfigRootDir: import.meta.dirname,
});

Peers / when not to use

  • Requires ESLint 9 flat config and TypeScript 5. Not for legacy .eslintrc alone.
  • Opinionated: bans most implementation comments. Do not adopt if your team relies on inline code commentary.
  • Not a runtime dependency of apps. Keep it in devDependencies.

Docs

License

MIT