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

be-pretty

v1.1.3

Published

:lipstick: adds prettier to an existing project with all bells and whistles-including husky, lint-staged

Downloads

2,322

Readme

be-pretty

fabolous

:lipstick: adds prettier to an existing project with all bells and whistles-including husky and pretty-quick. Have you ever been bothered by all the steps you need to do in a legacy codebase to get prettier all set up? Well now you don't have to.

Usage

When you are in an old codebase which needs to be pretty now, and stay pretty forever and ever execute npx be-pretty. An output should look like this:

be-pretty
  ✔ Installing prettier husky pretty-quick
  ✔ Copying custom .prettierrc
  ✔ Adding pretty-quick pre-commit to package.json
  ✔ Formatting whole repo

Now you should have everything ready to just commit&push.

You may skip formatting step with a flag --skipFormatting

Install(optional)

npm i be-pretty -g

Requires that you have npm/yarn/pnpm/bun and npx globally available. be pretty defaults to running npm, but if there is yarn.lock file it will use yarn.

Customize .prettierrc

by default, be-pretty creates this prettier config.

{
  "arrowParens": "always", // good for typescript/flow when you want to type your function arguments
  "singleQuote": true // IMHO better readability
}

if you want to customize this, just run be-pretty setDefault -p="/path/to/your/defaultPrettierRc". You can omit the path and if there is a prettierc file in the current working directory it will be used. be-pretty will use this as default from now on.

Format all

if you just want to reformat everything, you can call be-pretty formatAll

All Commands

  be-pretty setDefault  sets a .prettierrc file as your default, if ommited
                           will look for the .prettierrc file in CWD[aliases: d]
  be-pretty formatAll   formats everything excluding node_modules[aliases: f]
  be-pretty run         run the series of commands to make a codebase pretty
                                                                       [default]

FAQ

Will this work for a newly added languages as well?

Yes, the list of supported file extensions is not hardcoded anywhere-format all just invokes prettier in the current folder and let's it format all supported extensions.