‼️ feross/standard but with even more semicolon goodness
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.gitignore init;; Jul 30, 2015
.travis.yml init;; Jul 30, 2015
CHANGELOG.md init;; Jul 30, 2015
CONTRIBUTING.md init;; Jul 30, 2015
LICENSE.md init;; Jul 30, 2015
README.md update README;; Jul 30, 2015
bin.js init;; Jul 30, 2015
eslintrc.json update to latest standard Apr 12, 2017
index.js init;; Jul 30, 2015
options.js update to latest standard Apr 12, 2017
package.json 3.0.0 Apr 12, 2017



npm travis

This is feross/standard but even more semicolons!

Inspired by this part of great video by @shama.


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

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

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!


Contributions welcome! Please read the contributing guidelines first.