standard
Advanced tools
Changelog
[12.0.1] - 2018-08-29
standard
silently passes when run in Node 4, which matches the current behavior for Node 0.10, 0.12, and all other unsupported versions of Node.Changelog
[12.0.0] - 2018-08-28
New version of ESLint, new version of Standard!
When you upgrade, consider running standard --fix
to automatically format your code to match the newly added rules.
eslint
from ~4.19.0
to ~5.4.0
.
<></>
)(Estimated % of affected standard users, based on test suite in parens)
assert.equal()
, assert.deepEqual()
and assert.notEqual()
were deprecated in Node 10.None.
Changelog
[11.0.0] - 2018-02-18
This release has no new rules, but it does update to the latest version of eslint
,
version 4, which has some significant changes to existing rules. Most updates make
the indentation rules more strict.
Thankfully, most users will just need to run standard --fix
to update code to be
compliant.
Update eslint
from ~3.19.0 to ~4.18.0.
indent
rule is more strict.padded-blocks
rule is more strict.space-before-function-paren
rule is more strict.no-multi-spaces
rule is more strict.no-extra-parens
,no-unexpected-multiline
,no-regex-spaces
, andspace-unary-ops
Update eslint-plugin-import
from ~2.2.0
to ~2.8.0
import/*
rules.Update eslint-plugin-node
from ~4.2.2
to ~6.0.0
no-deprecated-api
rule is updated with Node.js 8 support and improved
Node 6 support.Upodate eslint-plugin-promise
from ~3.5.0
to ~3.6.0
.
Update eslint-plugin-react
from ~6.10.0
to ~7.6.1
jsx-indent
crashjsx-indent
indentation calculation with nested JSX.jsx-no-undef
will not check the global scope by default.jsx-curly-spacing
newline with object literals bug.jsx-curly-spacing
schema incompatibility with ESLint 4.2.0.jsx-indent
.//=
)
as errors. (spaced-comment) #918👏 Huge thanks to @Flet for putting together most of this release!
Changelog
[10.0.2] - 2017-04-14
standard
, so we are disabling it until its performance improves.Changelog
[10.0.0] - 2017-04-04
standard
just turned 10.0.0! 🎉
As with every new major release, there are lots of new rules in 10.0.0 designed to help catch bugs and make programmer intent more explicit.
standard
is more popular than ever – 330,000 downloads per month! It's even
more popular – 670,000 downloads per month – if you include the
shareable ESLint config
that we also publish.
The most important change in 10.0.0 is that using deprecated Node.js APIs is now considered an error. It's finally time to update those dusty old APIs!
Deprecated APIs are problematic because they may print warning messages in the console in recent versions of Node.js. This often confuses users and leads to unnecessary support tickets for project maintainers.
Some deprecated APIs are even insecure (or at least prone to incorrect usage) which
can have serious security implications. For that reason, standard
now considers
usage of Buffer(num)
to be an error, since this function returns uninitialized
program memory which could contain confidential information like passwords or keys.
Instead of Buffer(num)
, consider using Buffer.alloc(num)
or Buffer.from(obj)
which make the programmer's intent clearer. These functions exist in all currently
supported versions of Node.js, including Node.js 4.x. For more background,
see this Node.js issue.
We also improved some rules to support common patterns in code bases that use React, JSX, and Flow.
When you upgrade, consider running standard --fix
to automatically fix some of
the issues caught by this new version.
standard.lintTextSync
method(Estimated % of affected standard users, based on test suite in parens)
Buffer.from()
, Buffer.alloc()
) are used instead of Buffer()
callback
or cb
must be invoked with null
, undefined
, or an Error
as the first argumentError
object...rest
to omit properties from an object (no-unused-vars) #800
import type
statements (import/no-duplicates) #599
process.exit()
the same as throw
in code path analysis (node/process-exit-as-throw) #699