chore(deps): update dependency standard to v17 #60
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:
^11.0.1
->^17.0.0
Release Notes
standard/standard (standard)
v17.1.2
Compare Source
eslint-plugin-react
(#1976)004e63b
v17.1.1
Compare Source
7.35.2
(#1976)d535d98
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/#160v14.3.4
Compare Source
no-return-await
#1442v14.3.3
Compare Source
v14.3.2
Compare Source
eslint
to~6.8.0
v14.3.1
Compare Source
v14.3.0
Compare Source
eslint
to~6.4.0
v14.2.0
Compare Source
eslint
to~6.3.0
eslint-plugin-node
to~10.0.0
v14.1.0
Compare Source
BigInt
. #1378eslint
to6.2.2
to fix security issue (blog post) (security advisory)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 updatebabel-eslint
to10.0.3
or later for compatibility with this version ofstandard
.v14.0.2
Compare Source
v14.0.1
Compare Source
v14.0.0
Compare Source
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 yourcode to match the newly added rules.
standard
keeps growing! The latest stats show thatstandard
andeslint-standard-*
shareable configs are depended upon by 318,512 GitHubrepositories 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
*.mjs
and*.cjs
files automatically by default #1009.git/info/exclude
in addition to.gitignore
. #1277funding
, an open source funding experiment.Changed features
bundle.js
from the default list of ignored files #743New rules
(Estimated % of affected standard users, based on test suite in parens)
key
prop in JSX elements that likely require akey
prop (react/jsx-key) #1369 [1%]target='_blank'
in JSX links (react/jsx-no-target-blank) #1367 [0%]Changed rules
v13.1.0
Compare Source
eslint
from~6.0.1
to~6.1.0
v13.0.2
Compare Source
standard
not finding dependencies due to ESLint v6 plugin resolution change #1327 #1328 #1329v13.0.1
Compare Source
Changed rules
const
in destructuring when all variables are constant #1325v13.0.0
Compare Source
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'seven 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
eslint
from~5.16.0
to~6.0.1
standard
silently passes when run by an unsupported version of Node.eslint-config-standard
users only: Plugins are no longer affected byeslint
's locationeslint-plugin-promise
from~4.0.0
to~4.2.1
eslint-plugin-node
from~7.0.1
to~9.1.0
New rules
(Estimated % of affected standard users, based on test suite in parens)
const
instead oflet
if variable is never reassigned (prefer-const) #523 eslint-config-standard/#133 [14%]v12.0.1
Compare Source
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.v12.0.0
Compare Source
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
eslint
from~4.19.0
to~5.4.0
.<></>
)New rules
(Estimated % of affected standard users, based on test suite in parens)
assert.equal()
,assert.deepEqual()
andassert.notEqual()
were deprecated in Node 10.Changed rules
None.
Configuration
📅 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 was generated by Mend Renovate. View the repository job log.