Package Exports
- doublestandard
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (doublestandard) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
doublestandard
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
- Add it to
package.json
{
"name": "my-cool-package",
"devDependencies": {
"doublestandard": "^1.0.0"
},
"scripts": {
"test": "doublestandard && node my-tests.js"
}
}
- 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.
- 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.