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

@danydodson/prettier-config

v1.7.0

Published

Prettier configuration for JavaScript files

Downloads

23

Readme

prettier-config

npm

Mine prettier configuration.

Pairs well with mine ESLint configuration.

Installation

yarn

yarn add --dev prettier
yarn add --dev @danydodson/prettier-config prettier

npm

npm install --save-dev prettier
npm install --save-dev @danydodson/prettier-config

Usage

We export two ESLint configurations for your usage:

  1. Default
  2. Four Spaces

Default Config

Create a prettier.config.js file at the root of your project that contains:

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

Four Spaces Config

If you prefer 4 spaces instead of 2, use this in your prettier.config.js instead:

module.exports = require('@danydodson/prettier-config/four-spaces')

Pre-commit Hook

As another line of defense, if you want Prettier to automatically fix your errors on commit, you can use pretty-quick with husky, which manage git hooks.

yarn add --dev prettier pretty-quick husky
npm install --save-dev prettier pretty-quick husky

Update your package.json like this:

{
  "husky": {
    "hooks": {
      "pre-commit": "pretty-quick --staged"
    }
  }
}

If you already have lint-staged running ESLint on precommit, you can just add pretty-quick on top of it:

{
  "husky": {
    "hooks": {
      "pre-commit": "pretty-quick --staged && lint-staged"
    }
  },
  "lint-staged": {
    "*.js": ["eslint --fix", "git add"]
  }
}

Editor Integration

  • Visual Studio Code

    1. Install Prettier extension: View → Extensions then find and install Prettier - Code formatter.
    2. Reload the editor.
    3. In your user settings Code -> Preferences -> Settings add editor.formatOnSave: true.
  • Sublime Text 3

  • Atom

How to publish to npm

Read npm's docs on How to Update a Package.

  1. npm login
    • Make sure you're logged into Upstatement's npm account with the credentials from 1pass. npm whoami will tell you if you're already logged in.
  2. npm version <update_type>
    • update_type can be patch, minor, or major. If you don't know which one to use, go read about semantic versioning.
  3. npm publish

Enforced Rules

Check out all of Prettier's configuration options.

  • Print Width: Line wrap at 100 characters.

  • Tab Width: Spaces per indentation-level.

  • Tabs: Indent lines with spaces, not tabs.

  • Semicolons: Always print semicolons at the ends of statements.

    const greeting = 'hi'
  • Quote: Use single quotes instead of double quotes.

    const quote = 'single quotes are better'
  • Trailing Commas: Use trailing commas wherever possible.

    const obj = {
      a: 'hi',
      b: 'hey'
    }
  • Bracket Spacing: Print spaces between brackets in object literals.

    {
      foo: bar
    }
  • JSX Brackets: Put the > of a multi-line JSX element at the end of the last line instead of being alone on the next line (does not apply to self closing elements).

    <button className='prettier-class' id='prettier-id' onClick={this.handleClick}>
      Click Here
    </button>
  • Arrow Function Parentheses: Omit parens when possible.

    x => x