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.
eslint-config-standard from 17.0.0 to 17.1.0We'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!
eslint-config-node has been replaced with the up to date fork eslint-config-n. If you have used comments like // eslint-disable-line node/no-deprecated-api you now have to reference the n/ rules instead.object-shorthand rule (as warning)await #1548 #1775--verbose by defaulteslint from ~7.18.0 to ^8.13.0eslint-config-standard from 16.0.3 to 17.0.0 to adapt to ESLint 8eslint-config-standard-jsx from 10.0.0 to ^11.0.0 to adapt to ESLint 8standard-engine from ^14 to ^15.0.0 to adapt to ESLint 8, see its CHANGELOGeslint-plugin-node@~11.1.0 to eslint-plugin-n@^15.1.0 to adapt to ESLint 8eslint-plugin-import from ~2.24.2 to ^2.26.0eslint-plugin-promise from ~5.1.0 to ^6.0.0eslint-plugin-react from ~7.25.1 to ^7.28.017.0.0-1 #1775await #1548We'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.
eslint from ~7.18.0 to ^8.8.0eslint-config-standard from 16.0.3 to 17.0.0-0 to adapt to ESLint 8eslint-config-standard-jsx from 10.0.0 to 11.0.0-0 to adapt to ESLint 8standard-engine from ^14 to ^15.0.0-0 to adapt to ESLint 8, see its CHANGELOGeslint from ~7.13.1 to ~7.18.0eslint-config-standard from 16.0.2 to 16.0.3eslint-plugin-import from ~2.22.1 to ~2.24.2eslint-plugin-promise from ~4.2.1 to ~5.1.0eslint-plugin-react from ~7.21.5 to ~7.25.1eslint from ~7.12.1 to ~7.13.0standard to run on Node 11, even though it's not officially supported #1597standard 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.
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!
Massive improvements (on the order of minutes!) for projects with huge folders which are are ignored with .gitignore
🌟 Support the .gitignore ignore syntax from the command line #1117
standard src would not lint the src/ folderstandard src/**/*.js was requiredThis is now fixed! You can run standard src to lint the src/ folder!
🌟 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
--ext command line flag or in package.json:Example:
bash
standard --ext .ts
json
{
"standard": {
"extensions": [".ts"]
}
}
🌟 New cache directory location, respecting XDG_CACHE_HOME preference, with fallback to ~/.cache/standard standard-engine/#214
Update eslint from ~7.11.0 to ~7.12.1
Update standard-engine from ^12 to ^14
--help command which indicates that bundle.js is automatically ignored when it is not anymore standard-engine/#224Remove deglob package and use built-in ESLint folder-traversal support
Paths with square brackets (e.g. [ and ]) are no longer skipped #1333
blog/[slug].jsYou may notice new errors in these files since they were not being linted before
Better mono-repo support: Nested node_modules/ folders are ignored by default #1182
Remove eslint-plugin-standard #1316
no-callback-literal rule into eslint-plugin-node(Estimated % of affected standard users, based on test suite in parens)
Array method callbacks (array-callback-return) #859 [7%]RegExp constructor in favor of regular expression literals (prefer-regex-literals) #1413 [1%]case NaN, switch(NaN), indexOf(NaN), and lastIndexOf(NaN) (use-isnan) #1429 [0%]exports (node/no-exports-assign) #1400 [0%]ReactDOM.render (react/no-render-return-value) #1568 [1%]this.state (react/no-direct-mutation-state) #1571 [0%]findDOMNode (react/no-find-dom-node) #1570 [0%]isMounted (react/no-is-mounted) #1569 [0%]target='_blank' on any component named Link (react/jsx-no-target-blank) #1576 [0%]indent #1499indent rule eslint-config-standard/#177We'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.
export * as ns from 'source', and import.meta.Atomics, SharedArrayBuffer), ES 2020 (BigInt, BigInt64Array, BigUint64Array, globalThis), and ES 2021 (FinalizationRegistry, WeakRef). #1436 #1557 eslint-config-standard/#156standard silently passes when run by an unsupported version of Nodeeslint from ~6.8.0 to ~7.11.0(Estimated % of affected standard users, based on test suite in parens)
no-negated-in-lhs rule, already enforced by no-unsafe-negation eslint-config-standard/#160no-return-await #1442eslint to ~6.8.0eslint to ~6.4.0eslint to ~6.3.0eslint-plugin-node to ~10.0.0BigInt. #1378eslint to 6.2.2 to fix security issue (blog post) (security advisory)funding. See Recap of the funding 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.
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! 🚀
*.mjs and *.cjs files automatically by default #1009.git/info/exclude in addition to .gitignore. #1277funding, an open source funding experiment.bundle.js from the default list of ignored files #743(Estimated % of affected standard users, based on test suite in parens)
key prop in JSX elements that likely require a key prop (react/jsx-key) #1369 [1%]target='_blank' in JSX links (react/jsx-no-target-blank) #1367 [0%]eslint from ~6.0.1 to ~6.1.0standard not finding dependencies due to ESLint v6 plugin resolution change #1327 #1328 #1329const in destructuring when all variables are constant #1325Welcome 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! 🚀
eslint from ~5.16.0 to ~6.0.1standard silently passes when run by an unsupported version of Node.eslint-config-standard users only: Plugins are no longer affected by eslint's locationeslint-plugin-promise from ~4.0.0 to ~4.2.1eslint-plugin-node from ~7.0.1 to ~9.1.0(Estimated % of affected standard users, based on test suite in parens)
const instead of let if variable is never reassigned (prefer-const) #523 eslint-config-standard/#133 [14%]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.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.
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.
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.Minor improvements to:
no-extra-parens,no-unexpected-multiline,no-regex-spaces, andspace-unary-opsUpdate eslint-plugin-import from ~2.2.0 to ~2.8.0
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.
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!
standard, so we are disabling it until its performance improves.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) #800import type statements (import/no-duplicates) #599process.exit() the same as throw in code path analysis (node/process-exit-as-throw) #699+, -, *, /, %, and **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.
standard --fix(Estimated % of affected standard users, based on test suite in parens)
typeof expressions against string literals (valid-typeof) #629 [0%]standard --fixstandard --fixstandard --fixThe 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.
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.
standard --fixstandard --fixThis 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!
--fix command line flag #540 standard-engine/#107(Estimated % of affected standard users, based on test suite in parens)
babel users who use async generator functions.export so the following is allowed:js
import { foo } from 'bar'
export * from 'bar'
package.json (Reasoning is here)Estimated % of affected standard users, based on test suite
finally blocks (no-unsafe-finally) [0%]cwd (fixes #429)cwd (fixes snazzy/#8)The goal of this release is to make standard faster to install, and simpler to use.
standard-format (#340) (#397)standard-format, just install it separately: npm install -g standard-formatvirtual-dom or deku, and unecessarily tied standard to a single library.eslint-config-standard-jsx. The eslint-config-standard-react dependency was removed.The percentage (%) of users that rule changes will effect, based on real-world testing of the top ~400 npm packages is denoted in brackets.
__dirname/__filename string concatenation (#403) (no-path-concat) [5%]new Promise() is instantiated with the parameter names
resolve, reject (#282) (promise/param-names) [1%]* in yield * something (#335) (yield-star-spacing) [0%]package.jsonFor 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:
json
{
"standard": {
"plugins": [ "my-plugin" ]
}
}
no-return-assign behavior changed with arrow functions (eslint/eslint#5150)standard-engine change. Fix error tagline.eslint (its now moved to standard-engine)eslint from 1.1.0 to 1.3.1 (CHANGELOG)eslintrc.json to fix #226 and eslint-plugin-standard#3eslint 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.
no-extra-parens instead of the deprecated no-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.