-
Notifications
You must be signed in to change notification settings - Fork 1
fix(deps): update npm - all minor and patch updates #729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/npm-all-minor-and-patch-updates
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+2,167
−990
Conversation
This file contains hidden or 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
ac2eb9e
to
a468de6
Compare
a468de6
to
aeb663a
Compare
aeb663a
to
22d4653
Compare
22d4653
to
33ed149
Compare
33ed149
to
afe89dc
Compare
afe89dc
to
cd7cfe8
Compare
cd7cfe8
to
f0af754
Compare
f0af754
to
376476a
Compare
5753d92
to
f36d2a4
Compare
381702e
to
b7d3945
Compare
d34b958
to
ebc7b0b
Compare
1cb523f
to
6d3bf5e
Compare
6d3bf5e
to
e1c445a
Compare
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:
^2.0.3
->^2.0.15
^9.29.0
->^9.31.0
^0.60.1
->^0.62.0
^16.2.1
->^16.4.2
^0.7.7
->^0.7.8
^20.19.0
->^20.19.9
^8.34.0
->^8.38.0
^8.34.0
->^8.38.0
^5.2.0
->^5.2.1
^9.1.2
->^9.2.0
^17.0.1
->^17.2.0
^8.0.0
->^8.1.0
^9.29.0
->^9.31.0
^10.1.5
->^10.1.8
^5.4.1
->^5.5.3
^16.2.0
->^16.3.0
^11.6.0
->^11.7.1
^8.16.0
->^8.16.3
^3.5.3
->^3.6.2
^7.1.1
->^7.1.4
^7.10.0
->^7.12.0
Release Notes
eslint/eslint (@eslint/js)
v9.31.0
Compare Source
v9.30.1
Compare Source
v9.30.0
Compare Source
open-telemetry/opentelemetry-js-contrib (@opentelemetry/auto-instrumentations-node)
v0.62.0
Compare Source
Features
Dependencies
v0.61.0
Compare Source
⚠ BREAKING CHANGES
Features
Dependencies
polkadot-js/api (@polkadot/api)
v16.4.2
Compare Source
v16.4.1
Compare Source
v16.3.1
Compare Source
v16.2.2
Compare Source
Changes:
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.38.0
Compare Source
🩹 Fixes
isolatedDeclarations
if enabled inconstructor
option (#11351)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.37.0
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.36.0
Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.35.1
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.35.0
Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.38.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.37.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.36.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.35.1
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.35.0
Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
chaijs/chai (chai)
v5.2.1
Compare Source
What's Changed
Mostly internal changes but @SuperchupuDev realised the package.json
engines
field was out of date, so it has been updated to reflect that v5.0.0 onwards only supports Node >=18.no-var
rule and fix violations by @koddsson in https://github.com/chaijs/chai/pull/1675New Contributors
Full Changelog: chaijs/chai@v5.2.0...v5.2.1
open-cli-tools/concurrently (concurrently)
v9.2.0
Compare Source
What's Changed
--kill-timeout
by @gustavohenke in https://github.com/open-cli-tools/concurrently/pull/540New Contributors
Full Changelog: open-cli-tools/concurrently@v9.1.2...v9.2.0
motdotla/dotenv (dotenv)
v17.2.0
Compare Source
Added
DOTENV_CONFIG_QUIET=true
in your environment or.env
file to quiet the runtime log (#889)DOTENV_CONFIG_
environment variables take precedence over any code set options like({quiet: false})
v17.1.0
Compare Source
Added
af/envalid (envalid)
v8.1.0
Compare Source
It's been a little while, but a new stable release is here! Thanks to contributors for the following additions and fixes:
In addition, there have been some behind-the-scenes improvements:
eslint/eslint (eslint)
v9.31.0
Compare Source
v9.30.1
Compare Source
v9.30.0
Compare Source
prettier/eslint-config-prettier (eslint-config-prettier)
v10.1.8
Compare Source
eslint-config-prettier
10.1.5
Patch Changes
60fef02
Thanks @JounQin! - chore: addfunding
field intopackage.json
10.1.4
Patch Changes
94b4799
Thanks @silvenon! - fix(cli): do not crash on no rules configured10.1.3
Patch Changes
4e95a1d
Thanks @pilikan! - fix: this package iscommonjs
, align its types correctly10.1.2
Patch Changes
a8768bf
Thanks @Fdawgs! - chore(package): add homepage for some 3rd-party registry - see #321 for more details10.1.1
Patch Changes
#309
eb56a5e
Thanks @JounQin! - fix: separate the/flat
entry for compatibilityFor flat config users, the previous
"eslint-config-prettier"
entry still works, but"eslint-config-prettier/flat"
adds a newname
property for config-inspector, we just can't add it for the default entry for compatibility.See also #308
10.1.0
Minor Changes
56e2e34
Thanks @JounQin! - feat: migrate to exports field10.0.3
Patch Changes
#294
8dbbd6d
Thanks @FloEdelmann! - feat: add name to config#280
cba5737
Thanks @zanminkian! - feat: add declaration file10.0.2
Patch Changes
e750edc
Thanks @Fdawgs! - chore(package): explicitly declare js module type10.0.0
Major Changes
5be64be
Thanks @abrahamguo! - add support for @stylistic formatting rulesVersions before 10.0.0
Version 9.1.0 (2023-12-02)
ESLINT_CONFIG_PRETTIER_NO_DEPRECATED
environment variable.Version 9.0.0 (2023-08-05)
"unicode-bom": "off"
to your config to disable it again, or run ESLint with--fix
to fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@nstepien)!Version 8.10.0 (2023-08-03)
Version 8.9.0 (2023-07-27)
Version 8.8.0 (2023-03-20)
Version 8.7.0 (2023-03-06)
Version 8.6.0 (2023-01-02)
Version 8.5.0 (2022-03-02)
Version 8.4.0 (2022-02-19)
Version 8.3.0 (2021-04-24)
Version 8.2.0 (2021-04-13)
Version 8.1.0 (2021-02-24)
Version 8.0.0 (2021-02-21)
Changed: All configs have been merged into one!
To upgrade, change:
Into:
The
"prettier"
config now includes not just ESLint core rules, but also rules from all plugins. Much simpler!So … what’s the catch? Why haven’t we done this earlier? Turns out it’s just a sad mistake. I (@lydell) was confused when testing, and thought that turning off unknown rules in a config was an error. Thanks to Georgii Dolzhykov (@thorn0) for pointing this out!
If you use [eslint-plugin-prettier], all you need is [plugin:prettier/recommended]:
(The ["prettier/prettier" config][prettier-prettier-config] still exists separately. It’s the odd one out. The main
"prettier"
config does not include the rules from it.)Changed: The CLI helper tool now only prints warnings for [arrow-body-style] and [prefer-arrow-callback], just like other “special rules.” This means that if you’ve decided to use those rules and [eslint-plugin-prettier] at the same time, you’ll get warnings but exit code zero (success).
Version 7.2.0 (2021-01-18)
Version 7.1.0 (2020-12-19)
Version 7.0.0 (2020-12-05)
Changed: At least ESLint 7.0.0 is now required.
Changed: [arrow-body-style] and [prefer-arrow-callback] are no longer turned off by default. They only need to be turned off if you use [eslint-plugin-prettier]. If you do, add
"prettier/prettier"
to your"extends"
array to turn them off again.Alternatively, update [eslint-plugin-prettier] to version 3.2.0 or later which automatically turns off these two rules in its
"plugin:prettier/recommended"
config.The CLI helper tool only warns about these rules if you have the
"prettier/prettier"
rule enabled for a file.Changed:
no-tabs
is now a validatable rule. If you use it, you should enableallowIndentationTabs
so that the rule works regardless of your Prettier config:Changed: The CLI helper tool is now called just
eslint-config-prettier
instead ofeslint-config-prettier-check
. This is so thatnpx eslint-config-prettier
always works regardless of whether you have already installedeslint-config-prettier
or not: If you have, the local installation is used; if you haven’t,npx
downloads a temporary copy.Changed: The CLI helper tool no longer requires you to pipe the output of
eslint --print-config
to it. Instead, it does that automatically for you via ESLint API:s added in ESLint v7.Before:
After:
Improved: The npm package is now 75% smaller.
Version 6.15.0 (2020-10-27)
Version 6.14.0 (2020-10-21)
Version 6.13.0 (2020-10-16)
Version 6.12.0 (2020-09-25)
Version 6.11.0 (2020-04-21)
Version 6.10.1 (2020-03-22)
npx
when running the CLI helper tool.Version 6.10.0 (2020-01-28)
Version 6.9.0 (2019-12-27)
Version 6.8.0 (2019-12-25)
Version 6.7.0 (2019-11-19)
Version 6.6.0 (2019-11-17)
Version 6.5.0 (2019-10-26)
Version 6.4.0 (2019-10-05)
Version 6.3.0 (2019-09-10)
Version 6.2.0 (2019-09-03)
Version 6.1.0 (2019-08-19)
Version 6.0.0 (2019-06-25)
Changed: The CLI helper tool now considers [no-confusing-arrow] to conflict if you use the default value of its
allowParens
option. The default was changed totrue
in ESLint 6, which conflicts with Prettier.If the CLI helper tool gives you errors about this after upgrading, the solution is to change this:
Into this:
The latter works in both ESLint 6 as well as in ESLint 5 and older.
Improved:
eslint --print-config
usage instructions. The CLI tool help text as well as the documentation has been updated to suggest commands that work in ESLint 6.0 as well as in ESLint 5 and older. (Instead ofeslint --print-config .
, useeslint --print-config path/to/main.js
.)Version 5.1.0 (2019-06-25)
Version 5.0.0 (2019-06-15)
Removed: [react/self-closing-comp]. This rule was added in v4.1.0 not because it conflicted with Prettier but because it was unnecessary when using Prettier. However, in v1.18.0 [Prettier stopped converting empty elements to self-closing elements][prettier-self-closing]. So the rule is not unnecessary anymore.
If you use Prettier v1.17.1 or older you should be able to upgrade eslint-config-prettier to v5.0.0 without having to do anything else.
If you use Prettier v1.18.0 or newer, you might get lint errors about for example changing
<div></div>
into<div />
. You have two options:eslint --fix
if you prefer to enforce self-closing elements where possible. This should fix all the errors."react/self-closing-comp": "off"
to your ESLint config if you use autofix from your editor and you face the same [issue as Prettier did][prettier-self-closing].Changed: Node.js 6 is no longer officially supported, but v5.0.0 should still work with it.
Version 4.3.0 (2019-05-16)
Version 4.2.0 (2019-04-25)
Version 4.1.0 (2019-02-26)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At 12:00 AM through 04:59 AM and 10:00 PM through 11:59 PM, Monday through Friday ( * 0-4,22-23 * * 1-5 ), Only on Sunday and Saturday ( * * * * 0,6 ) in timezone Europe/London.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.