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

@ktsierra/prettier-config

v1.2.1

Published

My personal Prettier configurations

Readme

@ktsierra/prettier-config

My personal Prettier configuration for consistent code formatting across projects.

Installation

npm install -D @ktsierra/prettier-config prettier

Usage

To use this shared configuration in your project, create a prettier.config.mjs (or prettier.config.cjs) file at the root of your repository:

Note: It's important to use the .mjs extension for ESM configurations so that Node.js correctly interprets the file as an ES Module. Using .js will not work.

For ESM (.mjs)

import config from '@ktsierra/prettier-config';

export default config;

For CommonJS (`.cjs`)

module.exports = require('@ktsierra/prettier-config');

What's Included

  • No semicolons (`semi: false`)
  • Single quotes (`singleQuote: true`)
  • 2-space indentation (`tabWidth: 2`)
  • Trailing commas where valid in ES5 (`trailingComma: 'es5'`)
  • Bracket spacing enabled (`bracketSpacing: true`)
  • Brackets on new lines for JSX (`bracketSameLine: false`)
  • Line width set to 80 characters (`printWidth: 120`)

Example Configuration

/** @type {import("prettier").Config} */
export default {
  semi: false,
  singleQuote: true,
  tabWidth: 2,
  trailingComma: 'es5',
  bracketSpacing: true,
  bracketSameLine: false,
  printWidth: 120,
};

Extending or Overriding

If you want to customize the configuration further, you can extend it in your own `prettier.config.js`:

import baseConfig from '@ktsierra/prettier-config';

export default {
  ...baseConfig,
  // Your custom overrides
  printWidth: 100,
};

Why Use This?

  • Consistency: Enforces the same formatting rules across all your projects.
  • Simplicity: One shared config, easy to update and maintain.
  • Editor/CI Friendly: Works seamlessly with editors (like Neovim with prettierd) and CI pipelines.

Requirements

  • Prettier (added as a peer dependency)
  • Node.js 14 or newer

Feel free to open issues or PRs if you want to suggest improvements!