chore(deps): update dependency standard to v17 - abandoned
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| standard (source) | 14.3.4 -> 17.0.0 |
Release Notes
standard/standard
v17.0.0
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 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!
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)- Use of ESLint 8, which allows for support for all of the latest syntax that ESLint 8 includes, such as top level
await#1548 #1775 --verboseby default
Changed features
- Update
eslintfrom~7.18.0to^8.13.0 - Update
eslint-config-standardfrom16.0.3to17.0.0to adapt to ESLint 8 - Update
eslint-config-standard-jsxfrom10.0.0to^11.0.0to adapt to ESLint 8 - Update
standard-enginefrom^14to^15.0.0to adapt to ESLint 8, see itsCHANGELOG - Move from
eslint-plugin-node@~11.1.0toeslint-plugin-n@^15.1.0to adapt to ESLint 8 - Update
eslint-plugin-importfrom~2.24.2to^2.26.0 - Update
eslint-plugin-promisefrom~5.1.0to^6.0.0 - Update
eslint-plugin-reactfrom~7.25.1to^7.28.0
v16.0.4
- Update
eslintfrom~7.13.1to~7.18.0 - Update
eslint-config-standardfrom16.0.2to16.0.3 - Update
eslint-plugin-importfrom~2.22.1to~2.24.2 - Update
eslint-plugin-promisefrom~4.2.1to~5.1.0 - Update
eslint-plugin-reactfrom~7.21.5to~7.25.1
v16.0.3
- Update
eslintfrom~7.12.1to~7.13.0 - Relax rule: Enforce default parameters to be last #1414
v16.0.2
- Allow
standardto run on Node 11, even though it's not officially supported #1597
v16.0.1
- Introduce "warning" system for disruptive rules (read more below)
- Change rule to a "warning": Require let or const instead of var (no-var) #633
standard 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.
v16.0.0
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!
New features
-
🏎 Better performance: the filesystem doesn't need to be traversed multiple times! #1023
- Massive improvements (on the order of minutes!) for projects with huge folders which are are ignored with
.gitignore
- Massive improvements (on the order of minutes!) for projects with huge folders which are are ignored with
-
🌟 Support the
.gitignoreignore syntax from the command line #1117- In older versions, the command
standard srcwould not lint thesrc/folder - Instead, a glob pattern like
standard src/**/*.jswas required - This is now fixed! You can run
standard srcto lint thesrc/folder!
- In older versions, the command
-
🌟 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.cjs-
Can be configured with the
--extcommand line flag or inpackage.json: -
Example:
standard --ext .ts{ "standard": { "extensions": [".ts"] } }
-
-
🌟 New cache directory location, respecting
XDG_CACHE_HOMEpreference, with fallback to~/.cache/standardstandard-engine/#214
Changed features
-
Update
eslintfrom~7.11.0to~7.12.1 -
Update
standard-enginefrom^12to^14- Fix inaccurate
--helpcommand which indicates thatbundle.jsis automatically ignored when it is not anymore standard-engine/#224 - Remove
deglobpackage and use built-in ESLint folder-traversal support
- Fix inaccurate
-
Paths with square brackets (e.g.
[and]) are no longer skipped #1333- This pattern is particularly common in Next.js apps, e.g.
blog/[slug].js - You may notice new errors in these files since they were not being linted before
- This pattern is particularly common in Next.js apps, e.g.
-
Better mono-repo support: Nested
node_modules/folders are ignored by default #1182 -
Remove
eslint-plugin-standard#1316- We migrated the remaining
no-callback-literalrule intoeslint-plugin-node
- We migrated the remaining
New rules
(Estimated % of affected standard users, based on test suite in parens)
- Require let or const instead of var (no-var) #633 [75%] [automatic fixing reduces to 11%]
- Enforce return statements in
Arraymethod callbacks (array-callback-return) #859 [7%] - Disallow empty block statements (no-empty) #796 [2%]
- Enforce default parameters to be last (default-param-last) #1414 [1%]
- Disallow use of the
RegExpconstructor in favor of regular expression literals (prefer-regex-literals) #1413 [1%] - Disallow spaces inside of computed keys of class methods, getters and setters (computed-property-spacing) #1416 [0%]
- Disallow
case NaN,switch(NaN),indexOf(NaN), andlastIndexOf(NaN)(use-isnan) #1429 [0%] - Disallow assigning to imported bindings (no-import-assign) #1412 [0%]
- Enforce getter/setter pairs in classes (accessor-pairs) #1415 [0%]
- Node: Disallow assignment to
exports(node/no-exports-assign) #1400 [0%] - React: Prevent usage of the return value of
ReactDOM.render(react/no-render-return-value) #1568 [1%] - React: Prevent usage of deprecated methods (react/no-deprecated) #1572 [1%]
- React: Prevent direct mutation of
this.state(react/no-direct-mutation-state) #1571 [0%] - React: Prevent usage of
findDOMNode(react/no-find-dom-node) #1570 [0%] - React: Prevent usage of
isMounted(react/no-is-mounted) #1569 [0%] - React: Prevent using string refs (react/no-string-refs) #1567 [0%]
- JSX: Prevent missing parentheses around multiline JSX (react/jsx-wrap-multilines) #710 #1382 (0%)
- JSX: Check if shorthand fragment syntax requires a key prop (react/jsx-key) #1575 [0%]
- JSX: Prevent passing of children as props (react/no-children-prop) #1574 [0%]
- JSX: Prevent using children and dangerouslySetInnerHTML as props at the same time (react/no-danger-with-children) #1573 [0%]
- JSX: Prevent invalid characters from appearing in markup (react/no-unescaped-entities) #1566 [0%]
- JSX: Enforce JSX value is returned in component render function (react/require-render-return) #1565 [0%]
- JSX: Prevent usage of unsafe
target='_blank'on any component namedLink(react/jsx-no-target-blank) #1576 [0%]
Changed rules
- Relax rule: JSX: Consider the global scope when checking for defined Components #1115
- Relax rule: JSX: Remove conflicting indentation rule in
indent#1499
v15.0.1
- Relax rule: Remove conflicting JSX indenting with
indentrule eslint-config-standard/#177
v15.0.0
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 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.
New features
- Support ES 2021, the latest version of the ECMAScript specification, which includes support for logical assignment operators and numeric separators #1551
- Support ES 2020 features such as optional chaining, the nullish coalescing operator,
export * as ns from 'source', andimport.meta. - Support global variables from ES 2017 (
Atomics,SharedArrayBuffer), ES 2020 (BigInt,BigInt64Array,BigUint64Array,globalThis), and ES 2021 (FinalizationRegistry,WeakRef). #1436 #1557 eslint-config-standard/#156 - The documentation is now available in Indonesian 🇮🇩! #1544
- Thanks to @yoga1234 for the excellent work!
- Other community contributed translations exist in Spanish, French, Italian, Japanese, Korean, Portuguese, Simplified Chinese, and Taiwanese Mandarin.
- More translations are always welcome!
Changed features
- BREAKING: Node.js 8 is no longer supported
- Node.js 8 is EOL and will no longer be receiving security updates.
- To prevent breaking CI for projects which still support Node 8,
standardsilently passes when run by an unsupported version of Node
- Update
eslintfrom~6.8.0to~7.11.0
New rules
(Estimated % of affected standard users, based on test suite in parens)
- Require indentation for values of ternary expressions (indent) #927 [4%]
- Enforce newlines between operands of ternary expressions if the expression spans multiple lines (multiline-ternary) #1558 [3%]
- Disallow loops with a body that allows only one iteration (no-unreachable-loop) #1556 [0%]
- Disallow useless backreferences in regular expressions (no-useless-backreference) #1554 [0%]
- Enforce default clauses in switch statements to be last (default-case-last) #1553 [0%]
- Disallow Number Literals That Lose Precision (no-loss-of-precision) #1552 [0%]
Changed rules
- Relax rule: Allow function declarations in nested blocks #1406
- Relax rule: Removed redundant
no-negated-in-lhsrule, already enforced byno-unsafe-negationeslint-config-standard/#160
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.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
Deployment failed with the following error:
Environment Variable "JWT_SECRET" references Secret "jwt-secret", which does not exist.
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
Autoclosing Skipped
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.