Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[17.1.0] - 2023-05-29
- Update
eslint-config-standard
from17.0.0
to17.1.0
[17.0.0] - 2022-04-20
We're super excited to announce standard
17!
This major release fully focuses on getting in sync with the wider ESLint ecosystem and doesn't in itself introduce any new rules or features.
When you upgrade, consider running standard --fix
to automatically format your
code to match the current set of rules.
This is the first release by two of our standard
co-maintainers @Divlo and @voxpelli. Buy them a cake if you run into them, thanks for getting this release out!
Major changes
eslint-config-node
has been replaced with the up to date forkeslint-config-n
. If you have used comments like// eslint-disable-line node/no-deprecated-api
you now have to reference then/
rules instead.object-shorthand
rule (as warning)- Use of ESLint 8, which allows for support for all of the latest syntax that ESLint 8 includes, such as top level
await
#1548 #1775 --verbose
by default
Changed features
- Update
eslint
from~7.18.0
to^8.13.0
- Update
eslint-config-standard
from16.0.3
to17.0.0
to adapt to ESLint 8 - Update
eslint-config-standard-jsx
from10.0.0
to^11.0.0
to adapt to ESLint 8 - Update
standard-engine
from^14
to^15.0.0
to adapt to ESLint 8, see itsCHANGELOG
- Move from
eslint-plugin-node@~11.1.0
toeslint-plugin-n@^15.1.0
to adapt to ESLint 8 - Update
eslint-plugin-import
from~2.24.2
to^2.26.0
- Update
eslint-plugin-promise
from~5.1.0
to^6.0.0
- Update
eslint-plugin-react
from~7.25.1
to^7.28.0
[17.0.0-2] - 2022-02-03
- Fix: Follow up to the fix of #1548 in
17.0.0-1
#1775
[17.0.0-1] - 2022-01-31
- Fix: Ensure we support all of the latest syntax that ESLint 8 includes, such as top level
await
#1548
[17.0.0-0] - 2022-01-31
We're finally able to offer a pre-release of ESLint 8 based standard
17!
This major release fully focuses on getting in sync with the wider ESLint ecosystem and doesn't in itself introduce any new rules or features.
This pre-release exists to test out the ESLint 8 related changes and discover possible backwards incompatible changes that comes with it and mitigate unintended such before a stable release.
When you upgrade, consider running standard --fix
to automatically format your
code to match the current set of rules.
Changed features
- Update
eslint
from~7.18.0
to^8.8.0
- Update
eslint-config-standard
from16.0.3
to17.0.0-0
to adapt to ESLint 8 - Update
eslint-config-standard-jsx
from10.0.0
to11.0.0-0
to adapt to ESLint 8 - Update
standard-engine
from^14
to^15.0.0-0
to adapt to ESLint 8, see itsCHANGELOG
[16.0.4] - 2021-10-03
- Update
eslint
from~7.13.1
to~7.18.0
- Update
eslint-config-standard
from16.0.2
to16.0.3
- Update
eslint-plugin-import
from~2.22.1
to~2.24.2
- Update
eslint-plugin-promise
from~4.2.1
to~5.1.0
- Update
eslint-plugin-react
from~7.21.5
to~7.25.1
16.0.3 - 2020-11-17
- Update
eslint
from~7.12.1
to~7.13.0
- Relax rule: Enforce default parameters to be last #1414
16.0.2 - 2020-11-11
- Allow
standard
to run on Node 11, even though it's not officially supported #1597
16.0.1 - 2020-10-30
- Introduce "warning" system for disruptive rules (read more below)
- Change rule to a "warning": Require let or const instead of var (no-var) #633
standard
treats all rule violations as errors, which means that standard
will exit with a non-zero (error) exit code.
However, we may occasionally release a new major version of standard
which changes a rule that affects the majority of standard
users (for example,
transitioning from var
to let
/const
). We do this only when we think the
advantage is worth the cost and only when the rule is
auto-fixable.
In these situations, we have a "transition period" where the rule change is only
a "warning". Warnings don't cause standard
to return a non-zero (error)
exit code. However, a warning message will still print to the console. During
the transition period, using standard --fix
will update your code so that it's
ready for the next major version.
The slow and careful approach is what we strive for with standard
. We're
generally extremely conservative in enforcing the usage of new language
features. We want using standard
to be light and fun and so we're careful
about making changes that may get in your way. As always, you can
disable a rule at any time, if necessary.
16.0.0 - 2020-10-28
We're super excited to announce standard
16!
As with every new major release, there are lots of new rules in 16.0.0 designed to help catch bugs and make programmer intent more explicit. This release brings better performance, tons of bug fixes, improved JSX, React ⚛️, and Next.js support!
When you upgrade, consider running standard --fix
to automatically format your
code to match the newly added rules.
❤️ If you enjoy StandardJS and want to support future releases, please support Feross!
New features
-
🏎 Better performance: the filesystem doesn't need to be traversed multiple times! #1023
- Massive improvements (on the order of minutes!) for projects with huge folders which are are ignored with
.gitignore
- Massive improvements (on the order of minutes!) for projects with huge folders which are are ignored with
-
🌟 Support the
.gitignore
ignore syntax from the command line #1117- In older versions, the command
standard src
would not lint thesrc/
folder - Instead, a glob pattern like
standard src/**/*.js
was required - This is now fixed! You can run
standard src
to lint thesrc/
folder!
- In older versions, the command
-
🌟 Support relative paths from the command line in more situations (e.g.
standard ../src/*.js
) #1384 -
🌟 New
extensions
option for linting additional extensions besides.js
,.jsx
,.mjs
, and.cjs
-
Can be configured with the
--ext
command line flag or inpackage.json
: -
Example:
standard --ext .ts
{ "standard": { "extensions": [".ts"] } }
-
-
🌟 New cache directory location, respecting
XDG_CACHE_HOME
preference, with fallback to~/.cache/standard
standard-engine/#214
Changed features
-
Update
eslint
from~7.11.0
to~7.12.1
-
Update
standard-engine
from^12
to^14
- Fix inaccurate
--help
command which indicates thatbundle.js
is automatically ignored when it is not anymore standard-engine/#224 - Remove
deglob
package and use built-in ESLint folder-traversal support
- Fix inaccurate
-
Paths with square brackets (e.g.
[
and]
) are no longer skipped #1333- This pattern is particularly common in Next.js apps, e.g.
blog/[slug].js
- You may notice new errors in these files since they were not being linted before
- This pattern is particularly common in Next.js apps, e.g.
-
Better mono-repo support: Nested
node_modules/
folders are ignored by default #1182 -
Remove
eslint-plugin-standard
#1316- We migrated the remaining
no-callback-literal
rule intoeslint-plugin-node
- We migrated the remaining
New rules
(Estimated % of affected standard users, based on test suite in parens)
- Require let or const instead of var (no-var) #633 [75%][automatic fixing reduces to 11%]
- Enforce return statements in
Array
method callbacks (array-callback-return) #859 [7%] - Disallow empty block statements (no-empty) #796 [2%]
- Enforce default parameters to be last (default-param-last) #1414 [1%]
- Disallow use of the
RegExp
constructor in favor of regular expression literals (prefer-regex-literals) #1413 [1%] - Disallow spaces inside of computed keys of class methods, getters and setters (computed-property-spacing) #1416 [0%]
- Disallow
case NaN
,switch(NaN)
,indexOf(NaN)
, andlastIndexOf(NaN)
(use-isnan) #1429 [0%] - Disallow assigning to imported bindings (no-import-assign) #1412 [0%]
- Enforce getter/setter pairs in classes (accessor-pairs) #1415 [0%]
- Node: Disallow assignment to
exports
(node/no-exports-assign) #1400 [0%] - React: Prevent usage of the return value of
ReactDOM.render
(react/no-render-return-value) #1568 [1%] - React: Prevent usage of deprecated methods (react/no-deprecated) #1572 [1%]
- React: Prevent direct mutation of
this.state
(react/no-direct-mutation-state) #1571 [0%] - React: Prevent usage of
findDOMNode
(react/no-find-dom-node) #1570 [0%] - React: Prevent usage of
isMounted
(react/no-is-mounted) #1569 [0%] - React: Prevent using string refs (react/no-string-refs) #1567 [0%]
- JSX: Prevent missing parentheses around multiline JSX (react/jsx-wrap-multilines) #710 #1382 (0%)
- JSX: Check if shorthand fragment syntax requires a key prop (react/jsx-key) #1575 [0%]
- JSX: Prevent passing of children as props (react/no-children-prop) #1574 [0%]
- JSX: Prevent using children and dangerouslySetInnerHTML as props at the same time (react/no-danger-with-children) #1573 [0%]
- JSX: Prevent invalid characters from appearing in markup (react/no-unescaped-entities) #1566 [0%]
- JSX: Enforce JSX value is returned in component render function (react/require-render-return) #1565 [0%]
- JSX: Prevent usage of unsafe
target='_blank'
on any component namedLink
(react/jsx-no-target-blank) #1576 [0%]
Changed rules
- Relax rule: JSX: Consider the global scope when checking for defined Components #1115
- Relax rule: JSX: Remove conflicting indentation rule in
indent
#1499
15.0.1 - 2020-10-27
- Relax rule: Remove conflicting JSX indenting with
indent
rule eslint-config-standard/#177
15.0.0 - 2020-10-21
We're super excited to announce standard
15!
As with every new major release, there are lots of new rules in 15.0.0 designed to help catch bugs and make programmer intent more explicit. This release brings support for ES 2021, the latest version of the ECMAScript specification, as well as many quality-of-life improvements, including ESLint v7.
When you upgrade, consider running standard --fix
to automatically format your
code to match the newly added rules.
❤️ If you enjoy StandardJS and want to support future releases, check out Feross's GitHub Sponsors page.
New features
- Support ES 2021, the latest version of the ECMAScript specification, which includes support for logical assignment operators and numeric separators #1551
- Support ES 2020 features such as optional chaining, the nullish coalescing operator,
export * as ns from 'source'
, andimport.meta
. - Support global variables from ES 2017 (
Atomics
,SharedArrayBuffer
), ES 2020 (BigInt
,BigInt64Array
,BigUint64Array
,globalThis
), and ES 2021 (FinalizationRegistry
,WeakRef
). #1436 #1557 eslint-config-standard/#156 - The documentation is now available in Indonesian 🇮🇩! #1544
- Thanks to @yoga1234 for the excellent work!
- Other community contributed translations exist in Spanish, French, Italian, Japanese, Korean, Portuguese, Simplified Chinese, and Taiwanese Mandarin.
- More translations are always welcome!
Changed features
- BREAKING: Node.js 8 is no longer supported
- Node.js 8 is EOL and will no longer be receiving security updates.
- To prevent breaking CI for projects which still support Node 8,
standard
silently passes when run by an unsupported version of Node
- Update
eslint
from~6.8.0
to~7.11.0
New rules
(Estimated % of affected standard users, based on test suite in parens)
- Require indentation for values of ternary expressions (indent) #927 [4%]
- Enforce newlines between operands of ternary expressions if the expression spans multiple lines (multiline-ternary) #1558 [3%]
- Disallow loops with a body that allows only one iteration (no-unreachable-loop) #1556 [0%]
- Disallow useless backreferences in regular expressions (no-useless-backreference) #1554 [0%]
- Enforce default clauses in switch statements to be last (default-case-last) #1553 [0%]
- Disallow Number Literals That Lose Precision (no-loss-of-precision) #1552 [0%]
Changed rules
- Relax rule: Allow function declarations in nested blocks #1406
- Relax rule: Removed redundant
no-negated-in-lhs
rule, already enforced byno-unsafe-negation
eslint-config-standard/#160
14.3.4 - 2020-05-11
- Relax rule:
no-return-await
#1442
14.3.3 - 2020-03-15
- Skip running on versions of Node.js older than 8.10.0. #1496
14.3.2 - 2020-03-14
- Update
eslint
to~6.8.0
14.3.1 - 2019-09-17
- Skip running on versions of Node.js older than 8.6.0. #1418
14.3.0 - 2019-09-14
- Update
eslint
to~6.4.0
14.2.0 - 2019-09-11
- Update
eslint
to~6.3.0
- Update
eslint-plugin-node
to~10.0.0
14.1.0 - 2019-08-28
- Support ES 2020, the latest version of the ECMAScript specification, which includes support for Dynamic Imports and
BigInt
. #1378 - Security: Upgrade
eslint
to6.2.2
to fix security issue (blog post) (security advisory) - Remove
funding
. See Recap of thefunding
experiment for thoughts and learnings.
NOTE: If you use standard
with the --parser babel-eslint
option, please ensure that you update babel-eslint
to 10.0.3
or later for compatibility with this version of standard
.
14.0.2 - 2019-08-22
- Relax rule: Don't check indentation on template literal children (work around for ESLint bug) (indent) #1385
14.0.1 - 2019-08-22
- Relax rule (temporarily, to workaround a bug): Disallow missing parentheses around multiline JSX (react/jsx-wrap-multilines) #1382
14.0.0 - 2019-08-19
We're super excited to announce standard
14!
As with every new major release, there are lots of new rules in 14.0.0 designed
to help catch bugs and make programmer intent more explicit. This release brings
support for ES 2019, the latest version of the ECMAScript specification, as well
as many quality-of-life improvements for users who use tagged template strings,
JSX, and .mjs
files for ES modules.
When you upgrade, consider running standard --fix
to automatically format your
code to match the newly added rules.
standard
keeps growing! The latest stats show that standard
and
eslint-standard-*
shareable configs are depended upon by 318,512 GitHub
repositories and 33,349 public npm packages. Thanks for spreading the
word!
We now have a Discord server. Come chat with the maintainers, ask questions, and get help from the community!
❤️ If you enjoy StandardJS and want to support future releases, check out Feross's GitHub Sponsors page. GitHub is matching donations, so your dollars go twice as far! 🚀
New features
- Support ES 2019, the latest version of the ECMAScript specification. eslint-config-standard/e04e06
- Lint
*.mjs
and*.cjs
files automatically by default #1009 - Ignore patterns from
.git/info/exclude
in addition to.gitignore
. #1277 - Added
funding
, an open source funding experiment.
Changed features
- Remove
bundle.js
from the default list of ignored files #743
New rules
(Estimated % of affected standard users, based on test suite in parens)
- Require Dot Notation Whenever Possible (dot-notation) #1344 [6%]
- Require consistent line breaks inside braces (object-curly-newline) #782 [1%]
- Disallow template literals when placeholders or tagged template features are not used. (quotes) #838 eslint-config-standard/#151 [1%]
- Disallow lexical declarations in case/default clauses (no-case-declarations) #1211 eslint-config-standard/#137 [1%]
- Require the first JSX property to be placed on a new line if the JSX tag takes up multiple lines and there are multiple properties (react/jsx-first-prop-new-line) #696 [1%]
- Require linebreaks in curly braces in JSX attributes and expressions to be consistent (react/jsx-curly-newline) #1372 [1%]
- Require JSX attributes and logical expressions to be indented correctly (react/jsx-indent) #1370 [1%]
- Require JSX event handler names to follow conventions (react/jsx-handler-names) #1371 [1%]
- Disallow spaces inside of curly braces in JSX expressions in children (react/jsx-curly-spacing) #1373 [1%]
- Require JSX closing bracket to be aligned with the opening tag (react/jsx-closing-bracket-location) #1361 [1%]
- Disallow unnecessary curly braces in JSX props and children (react/jsx-curly-brace-presence) #1366 [1%]
- Disallow missing
key
prop in JSX elements that likely require akey
prop (react/jsx-key) #1369 [1%] - Disallow import of modules using absolute paths (import/no-absolute-path) #861 #1343 [0%]
- Require no spaces before JSX closing brackets (react/jsx-tag-spacing) #1348 eslint-config-standard-jsx/38 [0%]
- Disallow multiple spaces between inline JSX props (react/jsx-props-no-multi-spaces) #1363 [0%]
- Disallow accidental comments in JSX from being inserted as text nodes (react/jsx-no-comment-textnodes) #1368 [0%]
- Prevent usage of unsafe
target='_blank'
in JSX links (react/jsx-no-target-blank) #1367 [0%] - Require shorthand form for JSX fragments (react/jsx-fragments) #1364 [0%]
- Require PascalCase for user-defined JSX components (react/jsx-pascal-case) #1365 [0%]
- Require JSX closing tag to be aligned with the opening tag (react/jsx-closing-tag-location) #1358 [0%]
- Disallow missing parentheses around multiline JSX (react/jsx-wrap-multilines) #710 [0%]
- Require pipeline operators to appear at the start of a line (operator-linebreak) eslint-config-standard/#121 [0%]
- Disallow use of the void operator (no-void) eslint-config-standard/#135 [0%]
Changed rules
- Relax rule: Don't require newlines between single-line member functions or class field declarations (lines-between-class-members) #1347
- Relax rule: Don't check indentation on template literal children (work around for ESLint bug) (indent) #1176
- Relax rule: Disallow labels that are variables names (because all labels are already disallowed) (no-label-var) eslint-config-standard/#132
13.1.0 - 2019-07-20
- Update
eslint
from~6.0.1
to~6.1.0
13.0.2 - 2019-07-12
- Fix global installations of
standard
not finding dependencies due to ESLint v6 plugin resolution change #1327 #1328 #1329
13.0.1 - 2019-07-11
Changed rules
- Relax rule: Only enforce
const
in destructuring when all variables are constant #1325
13.0.0 - 2019-07-10
Welcome to the latest version of standard
!
As with every new major release, there are lots of new rules in 13.0.0 designed to help catch bugs and make programmer intent more explicit.
standard
is more popular than ever – 640,000 downloads per month! It's
even more popular – 3,000,000 downloads per month – if you include the
ESLint configuration
that we also publish (for advanced users).
When you upgrade, consider running standard --fix
to automatically format your code to match the newly added rules.
❤️ If you enjoy StandardJS and want to support future releases, check out Feross's GitHub Sponsors page. GitHub is matching donations, so your dollars go twice as far! 🚀
New features
- Update
eslint
from~5.16.0
to~6.0.1
- BREAKING: Node.js 6 is no longer supported
- Node.js 6 is EOL and will no longer be receiving security updates. As a result, the eslint team has decided to drop support for it.
- To prevent breaking CI for projects which still support Node 6,
standard
silently passes when run by an unsupported version of Node.
- For
eslint-config-standard
users only: Plugins are no longer affected byeslint
's location- Previously, ESLint loaded plugins relative to the location of the ESLint package itself. As a result, we suggested that users with global ESLint installations should also install plugins globally, and users with local ESLint installations should install plugins locally.
- With ESLint v6, plugins should always be installed locally, even if ESLint was installed globally. More precisely, ESLint v6 resolves plugins relative to the end user’s project by default, and always resolves shareable configs and parsers relative to the location of the config file that imports them.
- See migrating to ESLint 6.0.0 for more information.
- BREAKING: Node.js 6 is no longer supported
- The documentation is now available in Japanese 🇯🇵!
- Thanks to @munierujp for the excellent work!
- Other community contributed translations exist in Spanish, French, Italian, Korean, Portuguese, Simplified Chinese, and Taiwanese Mandarin.
- More translations are always welcome!
- Update
eslint-plugin-promise
from~4.0.0
to~4.2.1
- Update
eslint-plugin-node
from~7.0.1
to~9.1.0
New rules
(Estimated % of affected standard users, based on test suite in parens)
- Disallow spaces inside of array brackets (array-bracket-spacing) #1203 eslint-config-standard/#131 [14%]
- Require
const
instead oflet
if variable is never reassigned (prefer-const) #523 eslint-config-standard/#133 [14%] - Disallow quotes around object literal property names that are not strictly required (quote-props) #791 [4%]
- Disallow use of Object.prototypes builtins directly (no-prototype-builtins) #1310 [3%]
- Require an empty line between class members (lines-between-class-members) #438 [1%]
- Disallow using an async function as a Promise executor (no-async-promise-executor) #1309 [1%]
- Disallow spaces inside of computed properties (computed-property-spacing) #1315 eslint-config-standard/#131 [1%]
- Disallow unnecessary catch clauses (no-useless-catch) #1312 [0%]
- Disallow characters which are made with multiple code points in character class syntax (no-misleading-character-class) #1311 [0%]
12.0.1 - 2018-08-29
- Since ESLint 5 no longer supports Node 4,
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.
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.
New features
- Update
eslint
from~4.19.0
to~5.4.0
.- Support JSXFragment nodes (e.g.
<></>
) - Lots of minor changes to rules to catch more edge cases!
- Support JSXFragment nodes (e.g.
- The README is now available in French! (Thanks @charliegerard!)
- Other community contributed translations exist in Spanish, Italian, Korean, Portuguese, Simplified Chinese, and Taiwanese Mandarin.
- More translations are welcome!
New rules
(Estimated % of affected standard users, based on test suite in parens)
- Require spacing inside of braces (object-curly-spacing) #609 eslint-config-standard/#35 [29%]
- Disallow APIs that were deprecated in Node 10 (no-deprecated-api) #1164 [15%]
- e.g.
assert.equal()
,assert.deepEqual()
andassert.notEqual()
were deprecated in Node 10.
- e.g.
- Disallow self assignment of properties (no-self-assign) #1186 [0%]
- Disallow use of an exported name as the locally imported name of a default export (import/no-named-as-default) eslint-config-standard/#98
Changed rules
None.
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.
New features
-
Update
eslint
from ~3.19.0 to ~4.18.0.- The
indent
rule is more strict. - The
padded-blocks
rule is more strict. - The
space-before-function-paren
rule is more strict. - The
no-multi-spaces
rule is more strict. - Minor improvements to:
no-extra-parens
,no-unexpected-multiline
,no-regex-spaces
, andspace-unary-ops
- The
-
Update
eslint-plugin-import
from~2.2.0
to~2.8.0
- Updated for eslint 4.0 compatibility.
- Various small bug fixes included related to
import/*
rules.
-
Update
eslint-plugin-node
from~4.2.2
to~6.0.0
- The
no-deprecated-api
rule is updated with Node.js 8 support and improved Node 6 support.
- The
-
Upodate
eslint-plugin-promise
from~3.5.0
to~3.6.0
. -
Update
eslint-plugin-react
from~6.10.0
to~7.6.1
- Fix
jsx-indent
crash - Fix
jsx-indent
indentation calculation with nested JSX. - Fix
jsx-no-undef
will not check the global scope by default. - Fix
jsx-curly-spacing
newline with object literals bug. - Fix
jsx-curly-spacing
schema incompatibility with ESLint 4.2.0. - Fix alignment bug in
jsx-indent
.
- Fix
Changed rules
- Relax rule: Don't mark Rails Asset Pipeline comments (comments that start with
//=
) as errors. (spaced-comment) #918
👏 Huge thanks to @Flet for putting together most of this release!
10.0.3 - 2017-08-06
- Internal changes (incremented dependency versions)
10.0.2 - 2017-04-14
Changed rules
- Relax rule: Disallow import of modules using absolute paths (import/no-absolute-path) #861
- This rule was responsible for up to 25% of the running time of
standard
, so we are disabling it until its performance improves.
- This rule was responsible for up to 25% of the running time of
10.0.1 - 2017-04-06
- Internal changes (incremented dependency versions)
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.
New features
- Update ESLint from 3.15.x to 3.19.x.
- Node.js API: Add
standard.lintTextSync
method
New rules
(Estimated % of affected standard users, based on test suite in parens)
- Disallow using deprecated Node.js APIs (node/no-deprecated-api) #693 [13%]
- Ensures that code always runs without warnings on the latest versions of Node.js
- Ensures that safe Buffer methods (
Buffer.from()
,Buffer.alloc()
) are used instead ofBuffer()
- Enforce callbacks always called with Node.js-style error first (standard/no-callback-literal) #623 [3%]
- Functions named
callback
orcb
must be invoked withnull
,undefined
, or anError
as the first argument - Disallows using a string instead of an
Error
object - Disallows confusing callbacks that do not follow the standard Node.js pattern
- Functions named
- Disallow any imports that come after non-import statements (import/first) #806 [1%]
- Disallow unnecessary return await (no-return-await) #695 [0%]
- Disallow comma-dangle in functions (comma-dangle) #787 [0%]
- Disallow repeated exports of names or defaults (import/export) #806 [0%]
- Disallow import of modules using absolute paths (import/no-absolute-path) #806 [0%]
- Disallow Webpack loader syntax in imports (import/no-webpack-loader-syntax) #806 [0%]
- Disallow comparing against -0 (no-compare-neg-zero) #812 [0%]
Changed rules
- Relax rule: allow using
...rest
to omit properties from an object (no-unused-vars) #800- This is a common and useful pattern in React/JSX apps!
- Relax rule: allow Flow
import type
statements (import/no-duplicates) #599- These are no longer considered to be "duplicate imports"
- Relax rule: Treat
process.exit()
the same asthrow
in code path analysis (node/process-exit-as-throw) #699- Makes certain other rules work better and give fewer false positives
- Relax rule: allow Unnecessary Labels (no-extra-label)
- Redundant, since "no-labels" is already enabled, which is more restrictive
9.0.2 - 2017-03-17
Changed rules
- Relax rule: Allow tagged template string expressions (no-unused-expressions) #822
9.0.1 - 2017-03-07
Changed rules
- Relax rule: Allow mixing basic operators without parens (no-mixed-operators) #816
- Specifically, these operators:
+
,-
,*
,/
,%
, and**
- Specifically, these operators:
9.0.0 - 2017-02-28
It's time for a new major version of standard
! As usual, this release contains a
bunch of awesomeness to help you keep your code in tip-top shape!
We've added several new rules designed to catch potential programmer errors (i.e. bugs), as well as rules to make programmer intent more explicit in certain circumstances.
This release continues our trend of tightening up rules so that, wherever possible, there's one "right" way to do things. This design goal is intended to reduce the time that teams and maintainers spend giving code review feedback in pull requests.
When you upgrade, consider running standard --fix
to automatically fix some of the
errors caught by the new rules in this version.
Note: If you use the Chai test framework, you will need to make some changes to your tests to improve their robustness. Read about the changes you need to make.
New features
- Update ESLint from 3.10.x to 3.15.x
- 3 additional rules are now fixable with
standard --fix
New rules
(Estimated % of affected standard users, based on test suite in parens)
- Disallow mixing different operators without parens (no-mixed-operators) #566 [5%]
- Enforce 1 newline at end of file (previously 1 or 2 were ok) (no-multiple-empty-lines) #733 [3%]
- Disallow Unused Expressions (no-unused-expressions) #690 [3%]
- Note: this affects users of the Chai test framework. Read about the changes you need to make.
- Disallow redundant return statements (no-useless-return) #694 [1%]
- Disallow Incorrect Early Use (no-use-before-define) #636 [0%]
- Enforce that Promise rejections are passed an Error object as a reason (prefer-promise-reject-errors) #777 [0%]
- Enforce comparing
typeof
expressions against string literals (valid-typeof) #629 [0%] - Enforce spacing around * in generator functions (generator-star-spacing) #724 [0%]
- Disallow Unnecessary Labels (no-extra-label) #736 [0%]
- Disallow spacing between template tags and their literals (template-tag-spacing) #755 [0%]
- Disallow padding within switch statements and classes (padded-blocks) #610 [0%]
- Enforce that Symbols are passed a description (symbol-description) #630 [0%]
Changed rules
- Relax rule: allow TypeScript Triple-Slash Directives (spaced-comment) #660
- Relax rule: allow Flow Comments (spaced-comment) #661
8.6.0 - 2016-11-22
- Update ESLint from 3.8.x to 3.10.x
- 3 additional rules are now fixable with
standard --fix
8.5.0 - 2016-10-25
- Update ESLint from 3.7.x to 3.8.x
- 2 additional rules are now fixable with
standard --fix
8.4.0 - 2016-10-10
- Update ESLint from 3.6.x to 3.7.x
- 5 additional rules are now fixable with
standard --fix
- Use more conservative semver ranges #654
8.3.0 - 2016-09-29
The last release (8.2.0
) added ES7 support. This release (8.3.0
) adds ES8
support ...just 3 days later!
This release should eliminate the need to specify babel-eslint
as a custom
parser, since standard
can now parse ES8 (i.e. ES2017) syntax out of the box.
That means async
and await
will just work.
- Support ES8 (i.e. ES2017) syntax.
8.2.0 - 2016-09-26
For many users, this release should eliminate the need to specify babel-eslint
as
a custom parser, since standard
can now parse ES7 (i.e. ES2016) syntax out of the
box.
- Support ES7 (i.e. ES2016) syntax.
- Update ESLint from 3.5.x to 3.6.x
- 4 additional rules are now fixable with
standard --fix
8.1.0 - 2016-09-17
- Update ESLint from 3.3.x to 3.5.x
- Around 10 additional rules are now fixable with
standard --fix
8.0.0 - 2016-08-23
This release contains a bunch of goodies, including new rules that catch potential programmer errors (i.e. bugs) and enforce additional code consistency.
However, the best feature is surely the new --fix
command line flag to
automatically fix problems. If you ever used
standard-format
and ran into issues with the lack of ES2015+ support, you'll be happy about
--fix
.
standard --fix
is built into standard
v8.0.0 for maximum convenience, it
supports ES2015, and it's lightweight (no additional dependencies since it's part
of ESLint which powers standard
). Lots of problems are already fixable, and more
are getting added with each ESLint release.
standard
also outputs a message ("Run standard --fix
to automatically fix
some problems.") when it detects problems that can be fixed automatically so you
can save time!
With standard
v8.0.0, we are also dropping support for Node.js versions prior to
v4. Node.js 0.10 and 0.12 are in maintenance mode and will be unsupported at the
end of 2016. Node.js 4 is the current LTS version. If you are using an older
version of Node.js, we recommend upgrading to at least Node.js 4 as soon as
possible. If you are unable to upgrade to Node.js 4 or higher, then we recommend
continuing to use standard
v7.x until you are ready to upgrade Node.js.
Important: We will not be updating the standard
v7.x versions going forward.
All bug fixes and enhancements will land in standard
v8.x.
Full changelog below. Cheers!
New features
- Upgrade to ESLint v3 (https://eslint.org/docs/user-guide/migrating-to-3.0.0) #565
- BREAKING: Drop support for node < 4 (this was a decision made by the ESLint team)
- Expose ESLint's
--fix
command line flag #540 standard-engine/#107- Lightweight, no additional dependencies, fixes dozens of rules automatically
New rules
(Estimated % of affected standard users, based on test suite in parens)
- Enforce placing object properties on separate lines (object-property-newline) #524 [2%]
- Require block comments to be balanced (spaced-comment "balanced") #572 [2%]
- Disallow constant expressions in conditions (no-constant-condition) #563 [1%]
- Disallow renaming import, export, and destructured assignments to the same name (no-useless-rename) #537 [0%]
- Disallow spacing between rest and spread operators and their expressions (rest-spread-spacing) #567 [0%]
- Disallow the Unicode Byte Order Mark (BOM) (unicode-bom) #538 [0%]
- Disallow assignment to native objects/global variables (no-global-assign) #596 [0%]
- Disallow negating the left operand of relational operators (no-unsafe-negation) #595 [0%]
- Disallow template literal placeholder syntax in regular strings (no-template-curly-in-string) #594 [0%]
- Disallow tabs in file (no-tabs) #593 [0%]
Changed rules
- Relax rule: Allow template literal strings (backtick strings) to avoid escaping #421
- Relax rule: Do not enforce spacing around * in generator functions (#564 (comment))
- This is a temporary workaround for
babel
users who use async generator functions.
- This is a temporary workaround for
7.1.2 - 2016-06-03
- Fix install errors for some users by updating eslint peer dependency
7.1.1 - 2016-05-26
- Add back full node 0.10, 0.12 support
7.1.0 - 2016-05-16
- Upgrade eslint to version 2.10.2.
7.0.1 - 2016-05-04
- Relax "no-duplicate-imports" rule to not include
export
so the following is allowed:
import { foo } from 'bar'
export * from 'bar'
7.0.0 - 2016-05-02
Changes
- Upgrade eslint to version ~2.9.0
- Remove "rules" configuration option #367 from
package.json
(Reasoning is here)
New rules
Estimated % of affected standard users, based on test suite
- Require camelCase (camelcase) [4%]
- Disallow unnecessary escape usage (no-useless-escape) [4% -- but, including many bugs]
- Disallow duplicate imports (no-duplicate-imports) [0%]
- Disallow unmodified conditions of loops (no-unmodified-loop-condition) [0%]
- Disallow whitespace before properties (no-whitespace-before-property) [0%]
- Disallow control flow statements in
finally
blocks (no-unsafe-finally) [0%] - Disallow unnecessary computed property keys on objects (no-useless-computed-key) [0%]
- Validate spacing before closing bracket in JSX (react/jsx-space-before-closing) [0%]
Removed rules
- Require parens in arrow function arguments (arrow-parens)
6.0.8 - 2016-03-07
- Pin eslint to version ~2.2.0
- Update eslint-plugin-react to version 4.0.0
6.0.7 - 2016-02-18
- Revert: Use install location of standard as eslint
cwd
(fixes #429)
6.0.6 - 2016-02-18
- Use eslint 2.1.0
- Fix: Use install location of standard as eslint
cwd
(fixes snazzy/#8)
6.0.5 - 2016-02-12
- Use eslint 2.0.0 stable
6.0.4 - 2016-02-07
- Relax rule: Validate closing bracket location in JSX (jsx-closing-bracket-location)
6.0.3 - 2016-02-06
- Fix "Error: Cannot find module 'eslint-config-standard-jsx'" with npm 2 (node 0.10, 0.12, 4)
6.0.2 - 2016-02-06
- Internal change: Remove .eslintrc file, and use inline config
6.0.1 - 2016-02-05
- Internal change: Move .eslintrc file to root folder
6.0.0 - 2016-02-05
The goal of this release is to make standard
faster to install, and simpler to use.
Remove standard-format
(#340) (#397)
- Eliminates 250 packages, and cuts install time in half!
- For npm 2, install time goes from 20 secs —> 10 secs.
- For npm 3, install time goes from 24 secs —> 12 secs.
- To continue using
standard-format
, just install it separately:npm install -g standard-format
React-specific linting rules are removed (#351) (#367) (eslint-config-standard-react/#13)
- JSX is still supported, and it continues to be checked for style.
- There were only a few React-specific rules, but they made it extremely difficult for users of alternatives like
virtual-dom
ordeku
, and unecessarily tiedstandard
to a single library. - JSX rules come from
eslint-config-standard-jsx
. Theeslint-config-standard-react
dependency was removed.
New Rules
The percentage (%) of users that rule changes will effect, based on real-world testing of the top ~400 npm packages is denoted in brackets.
- Disallow
__dirname
/__filename
string concatenation (#403) (no-path-concat) [5%] - Require parens in arrow function arguments (#309) (arrow-parens) [5%]
- Ensure that
new Promise()
is instantiated with the parameter namesresolve
,reject
(#282) (promise/param-names) [1%] - Enforce Usage of Spacing in Template Strings (template-curly-spacing) [1%]
- Template strings are only allowed when necessary, i.e. template string features are being used (eslint got stricter: eslint/eslint#5147) [1%]
- Better dead code detection after conditional statements (eslint got stricter) [1%]
- Enforce spaces around
*
inyield * something
(#335) (yield-star-spacing) [0%] - Disallow labels on loops/switch statements too (made rule stricter) (no-labels) [0%]
- Disallow unnecessary constructor (no-useless-constructor) [0%]
- Disallow empty destructuring patterns (no-empty-pattern) [0%]
- Disallow Symbol Constructor (no-new-symbol) [0%]
- Disallow Self Assignment (no-self-assign) [0%]
Removed Rules
Expose eslint configuration via command line options and package.json
For power users, it might be easier to use one of these new hooks instead of forking
standard
, though that's still encouraged, too!
To set custom ESLint plugins, rules, or envs, use the command line --plugin
, --rules
, and --env
flags.
In package.json
, use the "standard" property:
{
"standard": {
"plugins": [ "my-plugin" ]
}
}
Upgrade to ESLint v2
- There may be slight behavior changes to existing rules. When possible, we've noted these in the "New Rules" and "Removed Rules" section.
Improve test suite
- Rule changes can be tested against every package on npm. For sanity, this is limited to packages with at least 4 dependents. Around 400 packages.
Known Issues
- Using prerelease eslint version (2.0.0-rc.0). There may be breaking changes before the stable release.
no-return-assign
behavior changed with arrow functions (eslint/eslint#5150)
Relevant diffs
- standard (v5.4.1...v6.0.0)
- eslint-config-standard (v4.4.0...v5.0.0)
- eslint-config-standard-jsx (v1.0.0)
- standard-engine (v2.2.4...v3.2.1)
5.4.1 - 2015-11-16
Fixed
- Fix for
standard-engine
change. Fix error tagline.
5.4.0 - 2015-11-16
Added
- [email protected]
- Disallow duplicate JSX properties
5.3.1 - 2015-09-18
Changed
5.3.0 - 2015-09-16
Changed
- [email protected] (history)
- [email protected] (history)
- [email protected] (history)
- [email protected] (history)
5.2.2 - 2015-09-08
Fixed
- We have a changelog now, and you're reading it!
- Minor README update
- Removed direct dependency on
eslint
(its now moved to standard-engine)
5.2.1 - 2015-09-03
Changed
- [email protected] (history)
- Revert rule: Disallow unncessary concatenation of strings
Fixed
- [email protected] (history)
- fix regression with ternary operator handling
5.2.0 - 2015-09-03
Added
- [email protected] (history)
- New rule: Disallow unncessary concatenation of strings
- New rule: Disallow duplicate name in class members
- New rule: enforce spaces inside of single line blocks
- Re-add rule: padded-blocks (Closes #170)
Changed
- Bump
eslint
from 1.1.0 to 1.3.1 (CHANGELOG) - [email protected] (history)
- A small change to make the plugin compatible with browserify which does not affect behavior.
Fixed
- [email protected] (CHANGELOG)
- Fix object rest/spread handling.
- Added white background to badge.svg to make it work with dark backgrounds (Closes #234)
- Minor updates to README.md
5.1.1 - 2015-08-28
Fixed
- Update to RULES.md to remove a missing hyperlink
- Add atom linter information to README.md
- Fixed duplicated word in the tagline message on the CLI
- Removed failing repository from tests (yoshuawuyts/initialize)
5.1.0 - 2015-08-14
Fixed
- [email protected] (history)
- Added rest/spread feature to
eslintrc.json
to fix #226 and eslint-plugin-standard#3
- Added rest/spread feature to
- [email protected] (CHANGELOG)
- Fix crash when propTypes don't have any parent
- Fix jsx-no-literals reporting errors outside JSX
Changed
- Bump eslint from 1.0.0 to 1.2.0 (CHANGELOG)
- Added more test repositories and disabled some that were failing
- Update bikeshedding link on README.md
5.0.2 - 2015-08-06
Changed
- [email protected] (history)
- Disable Rule: react/wrap-multilines
- Minor README updates
5.0.1 - 2015-08-05
5.0.0 - 2015-08-03
eslint v1.0.0 is released! eslint added some new rules that are nice, and lots of existing rules have subtle behavior changes designed to catch more errors.
Let's talk about the next version of standard! We bumped the major version to v5.0.0 to pull in these improvements.
New rules:
- space before/after arrow functions (https://github.com/feross/eslint-config-standard/commit/cf31561306f102b0772de55cd410b20912e733ee)
- indent switch "case" sections (https://github.com/feross/eslint-config-standard/commit/c6b10f68aa31e323933b14e04b50d8c1075ef28c)
- don't reassign class variable names (https://github.com/feross/eslint-config-standard/commit/96c727fdf917f213e23320cc9971a0e2e5bf2b7b)
- don't reassign const variables (https://github.com/feross/eslint-config-standard/commit/2dd1a09edcff6656731a394231e93850e55cc39d)
- don't use .call() or .apply() to invoke a function unless it's necessary (https://github.com/feross/eslint-config-standard/commit/6fba6e34d9281a716bf7ffc9fc5d804f6403f505)
Changed rules:
- use
no-extra-parens
instead of the deprecatedno-wrap-func
rule (https://github.com/feross/eslint-config-standard/commit/fc8a076c156d949b0b6046281f2e5f5c91e7da62) indent
got stricter and catches errors in object literal indentation. 12/131 repos in the test suite started failing after this rule was improved.