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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@u3u/prettier-config

v5.1.0

Published

🎨 The most perfect Prettier config

Downloads

777

Readme

My Prettier config

npm version npm downloads License

Features

  • Sort/merge import statements
  • Sort JSON Key
  • Sort package.json
  • Sort Tailwind CSS classes
  • Format jsdoc
  • Format nginx config
  • Extend config
  • ...

[!NOTE]

Upgrade this config to >=3.x version, Prettier should automatically infer the plugin parser. If you are using the prettier-vscode extension, you need to upgrade to >=9.17.0 version for automatic inference of the plugin parser to take effect.
See this fix: https://github.com/prettier/prettier-vscode/pull/3027

Install

pnpm add prettier @u3u/prettier-config -D

Usage

In your .prettierrc

"@u3u/prettier-config"

Use base config (without plugins)

"@u3u/prettier-config/base"

With Tailwind CSS (By default, the clsx, tw, and twMerge, twJoin methods will also be sorted.)

"@u3u/prettier-config/tw"

Add format script to package.json

{
  "scripts": {
    "format": "prettier --write ."
  }
}

Then you can run pnpm format to format all files.

Recommend VSCode Config

In your .vscode/settings.json

{
  "editor.defaultFormatter": "esbenp.prettier-vscode",
  "editor.formatOnSave": true,
  "prettier.documentSelectors": ["**/*"],
  "prettier.enableDebugLogs": true,
  "prettier.endOfLine": "lf",
  "prettier.printWidth": 120,
  "prettier.requireConfig": true,
  "prettier.semi": false,
  "prettier.singleQuote": true
}

Lint Staged

If you want to format before every commit, you can add the following to your package.json:

{
  "lint-staged": {
    "*": ["prettier --write --ignore-unknown"]
  },

  "simple-git-hooks": {
    "pre-commit": "npx lint-staged"
  }
}

then install them

pnpm add lint-staged simple-git-hooks -D
npx simple-git-hooks

Extend Config

In your .prettierrc.js

const { extendConfig } = require('@u3u/prettier-config/utils');

module.exports = extendConfig({
  printWidth: 80,
});

Global Default Format Config

You can place the config file in the user's home directory as the default config to format all files.

cd ~
pnpm add prettier @u3u/prettier-config -D
echo '"@u3u/prettier-config"' > '.prettierrc'

Related

License

MIT License © 2023 u3u