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

@harperdb/code-guidelines

v0.0.6

Published

Coding Guidelines for Harper repositories. Includes types, linting, and formatting.

Readme

@harperdb/code-guidelines

This repository contains code guideline tools and configurations for the HarperDB organization.

Currently exports shared configurations for Prettier, ESLint, and TS Node Type Checking. More tools will be added soon.

Quick Start

  1. npm i --save-dev @harperdb/code-guidelines

  2. Add "prettier": "@harperdb/code-guidelines/prettier" to package.json.

  3. Run npx prettier .

Formatting

We use Prettier for formatting. The default config is exported under the /prettier path (i.e. @harperdb/code-guidelines/prettier).

Review the Sharing Configurations documentation for more information how to use or extend the base config.

Linting

We use ESLint to enforce code quality and integrate Prettier formatting. The default config is exported under the /eslint path (i.e. @harperdb/code-guidelines/eslint).

Using the Harper ESLint Configuration

You must create a local ESLint configuration that imports Harper's ESLint configuration, then you can extend or override the base configuration by adding your own rules.

For more detailed information about extending configurations, see the ESLint Configuration Files documentation.

  1. Install the required dependencies:
npm i --save-dev @harperdb/code-guidelines eslint prettier
  1. Create an eslint.config.mjs file in your project root:
import harperConfig from '@harperdb/code-guidelines/eslint';
import { defineConfig } from 'eslint/config';

export default defineConfig([
	...harperConfig,
	// Your custom configuration here
	{
		rules: {
			// Override or add custom rules
		},
	},
]);
  1. Run ESLint:
npx eslint .

Type Checking

TypeScript configuration files are available under the /tsconfig export path and can be used with the extends property in your own tsconfig.json files.

For example, to use the base Node.js configuration (supporting Node.js v20 or later):

  1. Start by installing necessary dev dependencies:
   npm i --save-dev typescript @types/node@20 @harperdb/code-guidelines
  1. Then create a tsconfig.json file in your project with the following content:
{
	"extends": "@harperdb/code-guidelines/tsconfig.node.json",
	"compilerOptions": {
		// Your custom options here
	}
}
  1. Finally, use TypeScript or Node.js Type Stripping!
   npx tsc
   # or
   node src/index.ts

Configurations are based off of the popular tsconfig bases project.

The following list outlines the available configurations:

  • tsconfig.node.json - Node.js v20 or later with Node.js Type Stripping support
  • More coming soon!

Adding new configurations

To add a new TypeScript configuration:

  1. Create a new file in this repository starting with tsconfig. and ending with .json. The name in between should be descriptive of the environment or relevant version (e.g. tsconfig.react.json or tsconfig.node-24.json).
  2. Update the exports field in package.json to include the new configuration file using the same name as the file.
  3. Add it to the list above with a brief description.
  4. Ship it 🚀