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

@gushogg-blake/prettier-config

v1.0.0

Published

Prettier config

Downloads

4

Readme

Prettier config

This config enforces some suggestions for a simple way to approach code formatting, particularly when, how, and how much to indent.

Use tabs for indentation

Tabs are simpler (fewer characters) and more flexible (width can be set according to individual preference) than spaces, so it seems sensible to default to them unless there's a reason to use spaces.

One reason would be to align code to an arbitrary column, for example to have function arguments aligned like this:

doSomething(a,
            b);

...but if the next suggestion is also followed, that doesn't come up:

All multi-line constructions can follow the same simple rule for indentation

If something has opening and closing delimiters and becomes too long to put on one line, split it up like this:

  • The opening delimiter stays where it is (where it would be for a single-line construction).
  • The body starts on the next line, indented by one.
  • The closing delimiter goes on the next line after the body, at the same indentation as the opening line, i.e. one less than the body.
  • Subsequent code carries on from the closing delimiter, in some cases with an extra newline to give multi-line phrases some breathing room.

This works for functions, classes, loops, objects, arrays, function arguments (both calls and definitions), strings, and arbitrary expressions, for example big conditions joined by logical operators. For these expressions, if not already in the brackets of an if statement or other construct, use a pair of brackets as the opening and closing delimeters and start each line after the first with the operator that connects it to the previous line.

This makes code look consistent and avoids having to adjust indentation levels when things like function names change, as would be needed if the doSomething function from the previous example were renamed. The main practical disadvantage is that expressions take up slightly more vertical space when the closing delimiter is always on its own line.

Examples:

function fn(args) {
	doSomething();
	doSomething();
}

class A {
	constructor() {
		this.prop = 123;
	}
}

let obj = {
	a: 1,
	b: 2,
};

let array = [
	123,
	456,
];

let cond = (
	something
	&& somethingElse
	|| somethingElse
);

let cond = (
	something
	? somethingElse
	: somethingElse
);

function bigArgs(
	arg1,
	arg2,
) {
	doSomething();
	doSomething();
}

bigCall(
	123,
	456,
);

let str = `
	lorem ipsum
	dolor sit
	amet
`;

for (let i = 0; i < n; i++) {
	doSomething();
}