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

lower-standard4

v6.0.4-3

Published

JavaScript Lower Standard Style with 4-space indents

Downloads

2

Readme

JavaScript Lower Standard Style

This is a slightly less strict fork of standard

Install

npm install lower-standard

Rules

More relaxed than regular standard. Code should be enjoyable to write and pretty to look at. A lot of the big ticket items are the same as standard, for example:

  • 2 spaces – for indentation
  • Single quotes for strings – except to avoid escaping
  • No unused variables – this one catches tons of bugs!
  • No semicolons
  • Never start a line with ( or [
    • This is the only gotcha with omitting semicolons – automatically checked for you!
    • [More details][4]
  • Space after keywords if (condition) { ... }
  • Space after function name function name (arg) { ... }
  • Always use === instead of == – but obj == null is allowed to check null || undefined.
  • Always handle the node.js err function parameter
  • Always prefix browser globals with window – except document and navigator are okay
    • Prevents accidental use of poorly-named browser globals like open, length, event, and name.
  • And [more goodness][5]give standard a try today!

The biggest differences:

  • arrow parens if needed array.filter(x => x) is nicer to look at
  • stroustrup brace style down with 1tbs!
  • do not force curlys if (bool) doSomething() is nice looking
  • proper generator start position - function *sayHello() {}
  • line up key colons
  • allow case fallthroughs - why disable this feature? Just use if if you don't like it
  • no opinion on onevar