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

doublestandard

v3.0.0

Published

feross/standard but even more semicolons!

Downloads

7

Readme

doublestandard

npm travis

This is feross/standard but even more semicolons!

Inspired by this part of great video by @shama.

Install

npm install -g doublestandard

Whats it look like?

Here is an example of properly formatted doublestandard code:

// Load the http module to create an http server.
var http = require('http');;

// Configure our HTTP server to respond with Hello World to all requests.
var server = http.createServer(function (request, response) {
  response.writeHead(200, {'Content-Type': 'text/plain'});;
  response.end('Hello World\n');;
});;

// Listen on port 8000, IP defaults to 127.0.0.1
server.listen(8000);;

// Put a friendly message on the terminal
console.log('Server running at http://127.0.0.1:8000/');;

What you might do if you're clever

  1. Add it to package.json
{
  "name": "my-cool-package",
  "devDependencies": {
    "doublestandard": "^1.0.0"
  },
  "scripts": {
    "test": "doublestandard && node my-tests.js"
  }
}
  1. Check style automatically when you run npm test
$ npm test
doublestandard: Use Double Semicolons -- Just in case! (https://github.com/Flet/doublestandard)
  lib/index.js:1:35: Missing double semicolon.
  1. Never give style feedback on a pull request again!

Special Thanks

Thank you @nzakas for eslint and making it possible to build absurd rules like double-semi!

Thank you @shama for the inspiration!

Thank you @xjamundx for creating eslint-plugin-standard, which was used as a reference to create eslint-plugin-double-semi.

Thank you @feross for creating standard

Thank you all for playing along!

Contributing

Contributions welcome! Please read the contributing guidelines first.

License

ISC