chore(deps): update dependency standard to v17 #64
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
|
See the guidelines for reviewing dependency updates for info on how to review dependency update PRs. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^9.0.0->^17.0.0Release Notes
standard/standard (standard)
v17.1.2Compare Source
eslint-plugin-react(#1976)004e63bv17.1.1Compare Source
7.35.2(#1976)d535d98v17.1.0Compare Source
eslint-config-standardfrom17.0.0to17.1.0v17.0.0Compare Source
We're super excited to announce
standard17!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 --fixto automatically format yourcode to match the current set of rules.
This is the first release by two of our
standardco-maintainers @Divlo and @voxpelli. Buy them a cake if you run into them, thanks for getting this release out!Major changes
eslint-config-nodehas been replaced with the up to date forkeslint-config-n. If you have used comments like// eslint-disable-line node/no-deprecated-apiyou now have to reference then/rules instead.object-shorthandrule (as warning)await#1548 #1775--verboseby defaultChanged features
eslintfrom~7.18.0to^8.13.0eslint-config-standardfrom16.0.3to17.0.0to adapt to ESLint 8eslint-config-standard-jsxfrom10.0.0to^11.0.0to adapt to ESLint 8standard-enginefrom^14to^15.0.0to adapt to ESLint 8, see itsCHANGELOGeslint-plugin-node@~11.1.0toeslint-plugin-n@^15.1.0to adapt to ESLint 8eslint-plugin-importfrom~2.24.2to^2.26.0eslint-plugin-promisefrom~5.1.0to^6.0.0eslint-plugin-reactfrom~7.25.1to^7.28.0v16.0.4Compare Source
eslintfrom~7.13.1to~7.18.0eslint-config-standardfrom16.0.2to16.0.3eslint-plugin-importfrom~2.22.1to~2.24.2eslint-plugin-promisefrom~4.2.1to~5.1.0eslint-plugin-reactfrom~7.21.5to~7.25.1v16.0.3Compare Source
eslintfrom~7.12.1to~7.13.0v16.0.2Compare Source
standardto run on Node 11, even though it's not officially supported #1597v16.0.1Compare Source
standardtreats all rule violations as errors, which means thatstandardwill exit with a non-zero (error) exit code.
However, we may occasionally release a new major version of
standardwhich changes a rule that affects the majority of
standardusers (for example,transitioning from
vartolet/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
standardto return a non-zero (error)exit code. However, a warning message will still print to the console. During
the transition period,
using standard --fixwill 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
standardto 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.0Compare Source
We're super excited to announce
standard16!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 --fixto 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
.gitignoreignore syntax from the command line #1117standard srcwould not lint thesrc/folderstandard src/**/*.jswas requiredstandard srcto lint thesrc/folder!🌟 Support relative paths from the command line in more situations (e.g.
standard ../src/*.js) #1384🌟 New
extensionsoption for linting additional extensions besides.js,.jsx,.mjs, and.cjsCan be configured with the
--extcommand line flag or inpackage.json:Example:
{ "standard": { "extensions": [".ts"] } }🌟 New cache directory location, respecting
XDG_CACHE_HOMEpreference, with fallback to~/.cache/standardstandard-engine/#214Changed features
Update
eslintfrom~7.11.0to~7.12.1Update
standard-enginefrom^12to^14--helpcommand which indicates thatbundle.jsis automatically ignored when it is not anymore standard-engine/#224deglobpackage and use built-in ESLint folder-traversal supportPaths with square brackets (e.g.
[and]) are no longer skipped #1333blog/[slug].jsBetter mono-repo support: Nested
node_modules/folders are ignored by default #1182Remove
eslint-plugin-standard#1316no-callback-literalrule intoeslint-plugin-nodeNew rules
(Estimated % of affected standard users, based on test suite in parens)
Arraymethod callbacks (array-callback-return) #859 [7%]RegExpconstructor 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.1Compare Source
indentrule eslint-config-standard/#177v15.0.0Compare Source
We're super excited to announce
standard15!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 --fixto 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
standardsilently passes when run by an unsupported version of Nodeeslintfrom~6.8.0to~7.11.0New rules
(Estimated % of affected standard users, based on test suite in parens)
Changed rules
no-negated-in-lhsrule, already enforced byno-unsafe-negationeslint-config-standard/#160v14.3.4Compare Source
no-return-await#1442v14.3.3Compare Source
v14.3.2Compare Source
eslintto~6.8.0v14.3.1Compare Source
v14.3.0Compare Source
eslintto~6.4.0v14.2.0Compare Source
eslintto~6.3.0eslint-plugin-nodeto~10.0.0v14.1.0Compare Source
BigInt. #1378eslintto6.2.2to fix security issue (blog post) (security advisory)funding. See Recap of thefundingexperiment for thoughts and learnings.NOTE: If you use
standardwith the--parser babel-eslintoption, please ensure that you updatebabel-eslintto10.0.3or later for compatibility with this version ofstandard.v14.0.2Compare Source
v14.0.1Compare Source
v14.0.0Compare Source
We're super excited to announce
standard14!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
.mjsfiles for ES modules.When you upgrade, consider running
standard --fixto automatically format yourcode to match the newly added rules.
standardkeeps growing! The latest stats show thatstandardandeslint-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
*.mjsand*.cjsfiles automatically by default #1009.git/info/excludein addition to.gitignore. #1277funding, an open source funding experiment.Changed features
bundle.jsfrom the default list of ignored files #743New rules
(Estimated % of affected standard users, based on test suite in parens)
keyprop in JSX elements that likely require akeyprop (react/jsx-key) #1369 [1%]target='_blank'in JSX links (react/jsx-no-target-blank) #1367 [0%]Changed rules
v13.1.0Compare Source
eslintfrom~6.0.1to~6.1.0v13.0.2Compare Source
standardnot finding dependencies due to ESLint v6 plugin resolution change #1327 #1328 #1329v13.0.1Compare Source
Changed rules
constin destructuring when all variables are constant #1325v13.0.0Compare 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.
standardis 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 --fixto 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
eslintfrom~5.16.0to~6.0.1standardsilently passes when run by an unsupported version of Node.eslint-config-standardusers only: Plugins are no longer affected byeslint's locationeslint-plugin-promisefrom~4.0.0to~4.2.1eslint-plugin-nodefrom~7.0.1to~9.1.0New rules
(Estimated % of affected standard users, based on test suite in parens)
constinstead ofletif variable is never reassigned (prefer-const) #523 eslint-config-standard/#133 [14%]v12.0.1Compare Source
standardsilently 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.0Compare Source
New version of ESLint, new version of Standard!
When you upgrade, consider running
standard --fixto automatically format your code to match the newly added rules.New features
eslintfrom~4.19.0to~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.
v11.0.1Compare Source
v11.0.0Compare 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 --fixto update code to becompliant.
New features
Update
eslintfrom ~3.19.0 to ~4.18.0.indentrule is more strict.padded-blocksrule is more strict.space-before-function-parenrule is more strict.no-multi-spacesrule is more strict.no-extra-parens,no-unexpected-multiline,no-regex-spaces, andspace-unary-opsUpdate
eslint-plugin-importfrom~2.2.0to~2.8.0import/*rules.Update
eslint-plugin-nodefrom~4.2.2to~6.0.0no-deprecated-apirule is updated with Node.js 8 support and improvedNode 6 support.
Upodate
eslint-plugin-promisefrom~3.5.0to~3.6.0.Update
eslint-plugin-reactfrom~6.10.0to~7.6.1jsx-indentcrashjsx-indentindentation calculation with nested JSX.jsx-no-undefwill not check the global scope by default.jsx-curly-spacingnewline with object literals bug.jsx-curly-spacingschema 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.3Compare Source
v10.0.2Compare Source
Changed rules
standard, so we are disabling it until its performance improves.v10.0.1Compare Source
v10.0.0Compare Source
standardjust 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.
standardis 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,
standardnow 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 --fixto automatically fix some ofthe issues caught by this new version.
New features
standard.lintTextSyncmethodNew rules
(Estimated % of affected standard users, based on test suite in parens)
Buffer.from(),Buffer.alloc()) are used instead ofBuffer()callbackorcbmust be invoked withnull,undefined, or anErroras the first argumentErrorobjectChanged rules
...restto omit properties from an object (no-unused-vars) #800import typestatements (import/no-duplicates) #599process.exit()the same asthrowin code path analysis (node/process-exit-as-throw) #699Configuration
📅 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.