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

@aha-co/config

v1.2.0

Published

Standardized configs for Aha JS projects

Downloads

16

Readme

@aha-co/config

Standardized set of configuration files for TypeScript projects so we don't have to think about them. Heavily inspired by @epic-web/config.

Usage

These are a set of defaults and everything can be overridden as needed per project.

npm install @aha-co/config

TypeScript

Create a tsconfig.json file in the project root and extend this config file:

{
	"extends": ["@aha-co/config/typescript"],
	"include": ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx"],
	"compilerOptions": {
		// override here
	}
}

Create a reset.d.ts file:

import "@aha-co/config/reset.d.ts"

TS for Libraries

The configuration above assumes you're using a bundler to create an application. If you're creating a library, you'll want the configuration to be more strict to be consumable in as many setups as possible. You can extend a different config instead:

  extends: ["@aha-co/config/typescript.lib"],

ESLint

Create a eslint.config.js file in the project root and extend this config file:

import { config } from "@aha-co/config/eslint"

/** @type {import("eslint").Linter.Config[]} */
export default [
	...config,
	// override here
]

Prettier

Add a line in package.json to point to this config file:

  "prettier": "@aha-co/config/prettier",

You can add a .prettierignore file to your project root if needed.