standard
Advanced tools
The 'standard' npm package is a JavaScript style guide, linter, and formatter all in one. It enforces a consistent coding style without the need for configuration, making it easier to maintain code quality across projects.
Linting
Linting is the process of running a program that will analyze code for potential errors. The 'standard' package provides a zero-configuration linter that checks for style and programming errors.
npx standardAuto-fixing
The 'standard' package can automatically fix some of the issues it finds in your code. This feature helps in maintaining code quality by automatically correcting common style and formatting issues.
npx standard --fixIntegration with Editors
The 'standard' package can be integrated with various code editors like VSCode, Sublime Text, and Atom. This allows for real-time linting and auto-fixing as you write code.
/* Example for VSCode */
{
"editor.formatOnSave": true,
"javascript.validate.enable": false,
"standard.enable": true
}ESLint is a highly configurable linter for JavaScript and JSX. Unlike 'standard', which comes with a predefined set of rules, ESLint allows you to define your own rules or extend from popular style guides like Airbnb or Google.
Prettier is an opinionated code formatter that supports many languages. It focuses on code formatting rather than linting. While 'standard' includes both linting and formatting, Prettier is often used in conjunction with ESLint for a more comprehensive solution.
XO is a JavaScript linter with great defaults and minimal configuration. It is similar to 'standard' in that it aims to provide a zero-config experience, but it also allows for some customization and extends ESLint under the hood.
No decisions to make. No .eslintrc, .jshintrc, or .jscsrc files to manage. It just
works.
This module saves you (and others!) time in two ways:
npm install standard
( or [
if (condition) { ... }function name (arg) { ... }=== instead of == – but obj == null is allowed to check null || undefined.err function parameterwindow – except document and navigator are okay
open, length,
event, and name.standard a try today!To get a better idea, take a look at
a sample file written
in JavaScript Standard Style, or check out some of
the repositories that use
standard.
Use this in one of your projects? Include one of these badges in your readme to let people know that your code is using the standard style.
[](https://github.com/feross/standard)
[](http://standardjs.com/)
The easiest way to use JavaScript Standard Style to check your code is to install it
globally as a Node command line program. To do so, simply run the following command in
your terminal (flag -g installs standard globally on your system, omit it if you want
to install in the current working directory):
npm install standard -g
After you've done that you should be able to use the standard program. The simplest use
case would be checking the style of all JavaScript files in the current working directory:
$ standard
Error: Use JavaScript Standard Style
lib/torrent.js:950:11: Expected '===' and instead saw '=='.
You can optionally pass in a directory using the glob pattern:
$ standard src/util/**/*.js
Note: by default standard will look for all files matching the patterns: **/*.js, **/*.jsx.
First, install standard. Then, install the appropriate plugin for your editor:
Using Package Control, install SublimeLinter and SublimeLinter-contrib-standard.
For automatic formatting on save, install StandardFormat.
Install linter-js-standard.
For automatic formatting, install standard-formatter. For snippets, install standardjs-snippets.
Install Syntastic and add this line to .vimrc:
let g:syntastic_javascript_checkers = ['standard']
For automatic formatting on save, add these two lines to .vimrc:
autocmd bufwritepost *.js silent !standard % --format
set autoread
Install Flycheck and check out the manual to learn how to enable it in your projects.
Search the extension registry for "Standard Code Style".
Install vscode-standardjs.
For automatic formatting, install vscode-standard-format.
Both WebStorm and PhpStorm can be configured for Standard Style.
package.json{
"name": "my-cool-package",
"devDependencies": {
"standard": "^3.0.0"
},
"scripts": {
"test": "standard && node my-tests.js"
}
}
npm test$ npm test
Error: Use JavaScript Standard Style
lib/torrent.js:950:11: Expected '===' and instead saw '=='.
The beauty of JavaScript Standard Style is that it's simple. No one wants to maintain multiple hundred-line style configuration files for every module/project they work on. Enough of this madness!
This module saves you time in two ways:
Adopting standard style means ranking the importance of code clarity and community
conventions higher than personal style. This might not make sense for 100% of projects and
development cultures, however open source can be a hostile place for newbies. Setting up
clear, automated contributor expectations makes a project healthier.
No. The whole point of standard is to avoid bikeshedding about
style. There are lots of debates online about tabs vs. spaces, etc. that will never be
resolved. These debates just distract from getting stuff done. At the end of the day you
have to 'just pick something', and that's the whole philosophy of standard -- its a
bunch of sensible 'just pick something' opinions. Hopefully, users see the value in that
over defending their own opinions.
Of course it's not! The style laid out here is not affiliated with any official web
standards groups, which is why this repo is called feross/standard and not
ECMA/standard.
The word "standard" has more meanings than just "web standard" :-) For example:
Yes! Just run standard --format filename.js. This uses
Max Ogden's automatic formatter
standard-format, which can automatically
fix most code issues.
While most issues can be fixed, some, like not handling errors in node-style callbacks, must be fixed manually.
The paths node_modules/**, *.min.js, bundle.js, coverage/**, hidden files/folders
(beginning with .), and all patterns in a project's root .gitignore file are
automatically ignored.
Sometimes you need to ignore additional folders or specific minified files. To do that, add
a standard.ignore property to package.json:
"standard": {
"ignore": [
"**/out/",
"/lib/select2/",
"/lib/ckeditor/",
"tmp.js"
]
}
In rare cases, you'll need to break a rule and hide the warning generated by standard.
JavaScript Standard Style uses eslint under-the-hood and you can
hide warnings as you normally would if you used eslint directly.
To get verbose output (so you can find the particular rule name to ignore), run:
$ standard --verbose
Error: Use JavaScript Standard Style
routes/error.js:20:36: 'file' was used before it was defined. (no-use-before-define)
Disable all rules on a specific line:
file = 'I know what I am doing' // eslint-disable-line
Or, disable only the "no-use-before-define" rule:
file = 'I know what I am doing' // eslint-disable-line no-use-before-define
Or, disable the "no-use-before-define" rule for multiple lines:
/*eslint-disable no-use-before-define */
// offending code here...
// offending code here...
// offending code here...
/*eslint-enable no-use-before-define */
Some packages (e.g. mocha) put their functions (e.g. describe, it) on the global
object (poor form!). Since these functions are not defined or required anywhere in your
code, standard will warn that you're using a variable that is not defined (usually, this
rule is really useful for catching typos!). But we want to disable it for these global
variables.
To let standard (as well as humans reading your code) know that certain variables are
global in your code, add this to the top of your file:
/* global myVar1, myVar2 */
If you have hundreds of files, adding comments to every file can be tedious. In these
cases, you can add this to package.json:
{
"standard": {
"globals": [ "myVar1", "myVar2" ]
}
}
standard supports custom JS parsers. To use a custom parser, install it from npm
(example: npm install babel-eslint) and add this to your package.json:
{
"standard": {
"parser": "babel-eslint"
}
}
If you're using standard globally (you installed it with -g), then you also need to
install babel-eslint globally with npm install babel-eslint -g.
No. The point of standard is to save you time by picking reasonable rules so you can
spend your time solving actual problems. If you really do want to configure hundreds of
eslint rules individually, you can always use eslint directly.
If you just want to tweak a couple rules, consider using this shareable config and layering your changes on top.
Pro tip: Just use standard and move on. There are actual real problems that you could
spend your time solving! :P
Add this to the top of your files:
/* eslint-env serviceworker */
This lets standard (as well as humans reading your code) know that self is a global
in web worker code.
To support mocha in your test files, add this to the beginning of your test files:
/* eslint-env mocha */
Where mocha can be one of jasmine, qunit, phantomjs, and so on. To see a full list,
check ESLint's specifying environments
documentation. For a list of what globals are available for these environments, check
the globals npm module.
pre-commit hook?Funny you should ask!
#!/bin/sh
# Ensure all javascript files staged for commit pass standard code style
git diff --name-only --cached --relative | grep '\.js$' | xargs standard
exit $?
Alternatively, overcommit is a Git hook
manager that includes support for running standard as a Git pre-commit hook.
To enable this, add the following to your .overcommit.yml file:
PreCommit:
Standard:
enabled: true
The built-in output is simple and straightforward, but if you like shiny things, install snazzy:
npm install snazzy
And run:
$ standard --verbose | snazzy
There's also standard-tap, standard-json, and standard-reporter
standard. What packages should I know about?There are also many editor plugins, a list of
npm packages that use standard, and
an awesome list of
packages in the standard ecosystem.
standard.lintText(text, [opts], callback)Lint the provided source text to enforce JavaScript Standard Style. An opts object may
be provided:
var opts = {
globals: [], // global variables to declare
parser: '' // custom js parser (e.g. babel-eslint)
}
The callback will be called with an Error and results object:
var results = {
results: [
{
filePath: '',
messages: [
{ ruleId: '', message: '', line: 0, column: 0 }
],
errorCount: 0,
warningCount: 0
}
],
errorCount: 0,
warningCount: 0
}
standard.lintFiles(files, [opts], callback)Lint the provided files globs. An opts object may be provided:
var opts = {
globals: [], // global variables to declare
parser: '', // custom js parser (e.g. babel-eslint)
ignore: [], // file globs to ignore (has sane defaults)
cwd: '' // current working directory (default: process.cwd())
}
The callback will be called with an Error and results object (same as above).
Join us in #standard on freenode.
MIT. Copyright (c) Feross Aboukhadijeh.
[6.0.1] - 2016-02-05
FAQs
JavaScript Standard Style
The npm package standard receives a total of 394,098 weekly downloads. As such, standard popularity was classified as popular.
We found that standard demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 16 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.
Security News
The npm package for the LottieFiles Player web component was hit with a supply chain attack after a software engineer's npmjs credentials were compromised.