This repository was archived by the owner on Feb 13, 2025. It is now read-only.
Update dependency standard to v11 #2
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:
^4.5.4
->^11.0.0
By merging this PR, the below vulnerabilities will be automatically resolved:
Release Notes
standard/standard
v11.0.0
Compare Source
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 becompliant.
New features
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 improvedNode 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
.Changed rules
//=
)as errors. (spaced-comment) #918
👏 Huge thanks to @Flet for putting together most of this
release!
v10.0.3
Compare Source
v10.0.2
Compare Source
Changed rules
standard
, so we are disabling it until its performance improves.v10.0.1
Compare Source
v10.0.0
Compare Source
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 evenmore 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 considersusage of
Buffer(num)
to be an error, since this function returns uninitializedprogram memory which could contain confidential information like passwords or keys.
Instead of
Buffer(num)
, consider usingBuffer.alloc(num)
orBuffer.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 ofthe issues caught by this new version.
New features
standard.lintTextSync
methodNew rules
(Estimated % of affected standard users, based on test suite in parens)
Buffer.from()
,Buffer.alloc()
) are used instead ofBuffer()
callback
orcb
must be invoked withnull
,undefined
, or anError
as the first argumentError
objectChanged rules
...rest
to omit properties from an object (no-unused-vars) #800import type
statements (import/no-duplicates) #599process.exit()
the same asthrow
in code path analysis (node/process-exit-as-throw) #699v9.0.2
Compare Source
Changed rules
v9.0.1
Compare Source
Changed rules
+
,-
,*
,/
,%
, and**
v9.0.0
Compare Source
It's time for a new major version of
standard
! As usual, this release contains abunch 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 theerrors 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
standard --fix
New rules
(Estimated % of affected standard users, based on test suite in parens)
typeof
expressions against string literals (valid-typeof) #629 [0%]Changed rules
v8.6.0
Compare Source
standard --fix
v8.5.0
Compare Source
standard --fix
v8.4.0
Compare Source
standard --fix
v8.3.0
Compare Source
The last release (
8.2.0
) added ES7 support. This release (8.3.0
) adds ES8support ...just 3 days later!
This release should eliminate the need to specify
babel-eslint
as a customparser, since
standard
can now parse ES8 (i.e. ES2017) syntax out of the box.That means
async
andawait
will just work.v8.2.0
Compare Source
For many users, this release should eliminate the need to specify
babel-eslint
asa custom parser, since
standard
can now parse ES7 (i.e. ES2016) syntax out of thebox.
standard --fix
v8.1.0
Compare Source
standard --fix
v8.0.0
Compare Source
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 toautomatically 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 intostandard
v8.0.0 for maximum convenience, itsupports ES2015, and it's lightweight (no additional dependencies since it's part
of ESLint which powers
standard
). Lots of problems are already fixable, and moreare getting added with each ESLint release.
standard
also outputs a message ("Runstandard --fix
to automatically fixsome 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 tov4. 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
--fix
command line flag #540 standard-engine/#107New rules
(Estimated % of affected standard users, based on test suite in parens)
Changed rules
babel
users who use async generator functions.v7.1.2
Compare Source
v7.1.1
Compare Source
v7.1.0
Compare Source
v7.0.1
Compare Source
export
so the following is allowed:v7.0.0
Compare Source
17.0.0-1
#1775v6.0.8
Compare Source
v6.0.7
Compare Source
cwd
(fixes #429)v6.0.6
Compare Source
cwd
(fixes snazzy/#8)v6.0.5
Compare Source
v6.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
v6.0.3
Compare Source
eslint
from~7.12.1
to~7.13.0
v6.0.2
Compare Source
standard
to run on Node 11, even though it's not officially supported #1597v6.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.
v6.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
#1499v5.4.1
Compare Source
view diff
Fixed
standard-engine
change. Fix error tagline.v5.4.0
Compare Source
view diff
Added
v5.3.1
Compare Source
view diff
Changed
v5.3.0
Compare Source
view diff
Changed
v5.2.2
Compare Source
view diff
Fixed
eslint
(its now moved to standard-engine)v5.2.1
Compare Source
view diff
Changed
Fixed
v5.2.0
Compare Source
view diff
Added
Changed
eslint
from 1.1.0 to 1.3.1 ([CHANGELOG][eslint])Fixed
v5.1.1
Compare Source
view diff
Fixed
v5.1.0
Compare Source
view diff
Fixed
eslintrc.json
to fix #226 and eslint-plugin-standard#3Changed
v5.0.2
Compare Source
view diff
Changed
v5.0.1
Compare Source
indent
rule eslint-config-standard/#177v5.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/#160