Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^14.3.0
->^17.0.0
Release Notes
standard/standard (standard)
v17.1.0
Compare Source
eslint-config-standard
from17.0.0
to17.1.0
v17.0.0
Compare Source
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 yourcode 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)await
#1548 #1775--verbose
by defaultChanged features
eslint
from~7.18.0
to^8.13.0
eslint-config-standard
from16.0.3
to17.0.0
to adapt to ESLint 8eslint-config-standard-jsx
from10.0.0
to^11.0.0
to adapt to ESLint 8standard-engine
from^14
to^15.0.0
to adapt to ESLint 8, see itsCHANGELOG
eslint-plugin-node@~11.1.0
toeslint-plugin-n@^15.1.0
to adapt to ESLint 8eslint-plugin-import
from~2.24.2
to^2.26.0
eslint-plugin-promise
from~5.1.0
to^6.0.0
eslint-plugin-react
from~7.25.1
to^7.28.0
v16.0.4
Compare Source
eslint
from~7.13.1
to~7.18.0
eslint-config-standard
from16.0.2
to16.0.3
eslint-plugin-import
from~2.22.1
to~2.24.2
eslint-plugin-promise
from~4.2.1
to~5.1.0
eslint-plugin-react
from~7.21.5
to~7.25.1
v16.0.3
Compare Source
eslint
from~7.12.1
to~7.13.0
v16.0.2
Compare Source
standard
to run on Node 11, even though it's not officially supported #1597v16.0.1
Compare Source
standard
treats all rule violations as errors, which means thatstandard
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
tolet
/const
). We do this only when we think theadvantage 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'sready for the next major version.
The slow and careful approach is what we strive for with
standard
. We'regenerally extremely conservative in enforcing the usage of new language
features. We want using
standard
to be light and fun and so we're carefulabout making changes that may get in your way. As always, you can
disable a rule at any time, if necessary.
v16.0.0
Compare Source
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 yourcode 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
.gitignore
🌟 Support the
.gitignore
ignore syntax from the command line #1117standard src
would not lint thesrc/
folderstandard src/**/*.js
was requiredstandard src
to lint thesrc/
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
Can be configured with the
--ext
command line flag or inpackage.json
:Example:
🌟 New cache directory location, respecting
XDG_CACHE_HOME
preference, with fallback to~/.cache/standard
standard-engine/#214Changed features
Update
eslint
from~7.11.0
to~7.12.1
Update
standard-engine
from^12
to^14
--help
command which indicates thatbundle.js
is automatically ignored when it is not anymore standard-engine/#224deglob
package and use built-in ESLint folder-traversal supportPaths with square brackets (e.g.
[
and]
) are no longer skipped #1333blog/[slug].js
Better mono-repo support: Nested
node_modules/
folders are ignored by default #1182Remove
eslint-plugin-standard
#1316no-callback-literal
rule intoeslint-plugin-node
New rules
(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)
, andlastIndexOf(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 namedLink
(react/jsx-no-target-blank) #1576 [0%]Changed rules
indent
#1499v15.0.1
Compare Source
indent
rule eslint-config-standard/#177v15.0.0
Compare Source
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 yourcode 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
export * as ns from 'source'
, andimport.meta
.Atomics
,SharedArrayBuffer
), ES 2020 (BigInt
,BigInt64Array
,BigUint64Array
,globalThis
), and ES 2021 (FinalizationRegistry
,WeakRef
). #1436 #1557 eslint-config-standard/#156Changed features
standard
silently passes when run by an unsupported version of Nodeeslint
from~6.8.0
to~7.11.0
New rules
(Estimated % of affected standard users, based on test suite in parens)
Changed rules
no-negated-in-lhs
rule, already enforced byno-unsafe-negation
eslint-config-standard/#160Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.