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

@frostbitecms/prettier

v1.0.2

Published

frostbitecms prettier config rules

Downloads

3

Readme

Frostbite prettier rules

Install with npm

npm i -D @frostbitecms/prettier

with yarn

yarn add -D @frostbitecms/prettier

use in package.json

{
  "prettier": "@frostbitecms/prettier"
}

will add the rules for the formatter

Rationale

rule | value | reason ----|-------|---- arrowParens | always |this is for consistency, i dont really like one liners usually and will just prefer function() anyway, but in react this rule makes it easier to read bracketSameLine | true | i think it looks really weird when the > character is on its own line bracketSpacing | true | improves readability of object properties embeddedLanguageFormatting | auto | its usually alright about getting this right but it isn't really a big deal to begin with endOfLine | lf | this is for git consistency with diffs since ultimately windows is not a production environment or a "git environment" jsxSingleQuote, singleQuote | true | i like to make the lines less wide so that more can fit on the screen without a horizontal scroll in a multi-window environment printWidth | 90 | 80 is a bit low, 100 is too wide for multi-window workspaces but 90 is a nice middle ground semi | true | ending a statement explicitly when you can is just better trailingComma | none | just looks more neat when it doesn't "trail off" useTabs | true | consistency for people's custom tab width preferences (i prefer 2 personally for the same reasons as quotes) quoteProps | as-needed | ideally we dont need to quote object keys in sourcecode but if we need to we need to