chore(deps): update all non-major dependencies #154
Merged
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:
^18.14.1
->^18.15.0
^0.28.5
->^0.29.2
^0.4.1
->^0.5.1
^8.34.0
->^8.35.0
^1.17.1
->^1.17.2
7.27.1
->7.29.1
^1.1.0
->^1.1.1
^0.28.5
->^0.29.2
Release Notes
vitest-dev/vitest
v0.29.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.29.0
Compare Source
This release makes some significant changes to how tests are running. If you were using
--no-threads
before, you might consider enabling--single-thread
instead (because your tests are now running inchild_process
instead of a worker thread) or try our new performance optimization feature (discussed later). If you were relying on API that was not available inside a worker (likeprocess.chdir()
, you can now use this option.One of the potential breaking bug fixes is that environments do not share the same global scope anymore if you run them with
--no-isolate
,--no-threads
or--single-thread
- you might need to update your setup files if you were relying on a global variable before.If you had performance issues on large code bases before, try the new
deps.experimentalOptimizer
option instead of disabling threads. Feedback is welcome!One of the breaking changes includes adding a link to snapshots inside snapshot files, meaning you will need to update all your snapshots.
🚨 Breaking Changes
NODE_V8_COVERAGE
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2786 (095c6)node
andjsdom
(and other environments) now don't share the same global scope, if you run them with--no-isolate
or--no-threads
flag. Vitest doesn't provide a way to restore the previous behavior as it is considered a bug.chid_process
might run longer due to the communication overhead. If you want to restore the previous behavior, use--single-thread
.🚀 Features
🐞 Bug Fixes
View changes on GitHub
unjs/changelogen
v0.5.1
Compare Source
compare changes
🩹 Fixes
🏡 Chore
❤️ Contributors
v0.5.0
Compare Source
compare changes
🚀 Enhancements
gh release
to latest version (44788f5)🩹 Fixes
CHANGELOG.md
andpackage.json
when releasing (69d375c)-*
arg (77b483b)🏡 Chore
❤️ Contributors
eslint/eslint
v8.35.0
Compare Source
Features
8e34a04
feat: addafterHashbangComment
option tolines-around-comment
rule (#16920) (SUZUKI Sosuke)c8c0c71
feat: Move all and recommended configs into package. (#16844) (Nicholas C. Zakas)71f6f0d
feat: report more cases with??
in no-constant-binary-expression (#16826) (Daiki Nishikawa)Bug Fixes
9698bc5
fix: pin esquery v1.4.0 (fixes #16896) (#16897) (唯然)Documentation
f9f195e
docs: Plugin docs cleanup & expansion (#16862) (Ben Perlmutter)df809fd
docs: Custom Formatters page cleanup/expansion (#16886) (Ben Perlmutter)0700d1b
docs: Add PostCSS/Autoprefixer/CSSNano (#16502) (Nick Schonning)7b9e9bf
docs: support unicode anchors (#16782) (Percy Ma)5fbc0bf
docs: Update README (GitHub Actions Bot)67865a0
docs: Remove mention of mailing list (#16869) (Amaresh S M)43af24a
docs: Add explanation of when to use 'warn' severity (#16882) (Nicholas C. Zakas)ed2999b
docs: Shareable configs page edits and expansion (#16824) (Ben Perlmutter)2780635
docs: fix typos (#16884) (Lioness100)5bdaae2
docs: Ways to Extend ESLint page (#16861) (Ben Perlmutter)Chores
cdcbe12
chore: upgrade @eslint/js@8.35.0 (#16935) (Brandon Mills)c954c34
chore: package.json update for @eslint/js release (ESLint Jenkins)5a517da
chore: package.json update for @eslint/js release (ESLint Jenkins)9f10926
chore: upgrade @eslint/eslintrc@2.0.0 (#16928) (Milos Djermanovic)da728fa
ci: use LTS node version in workflows (#16907) (Nitin Kumar)c57b4f3
perf: upgrade to esquery@1.4.2 (#16901) (Milos Djermanovic)9122f07
chore: Update stale bot settings (#16870) (Nicholas C. Zakas)unjs/jiti
v1.17.2
Compare Source
compare changes
🩹 Fixes
TMPDIR
(#123)🏡 Chore
✅ Tests
🎨 Styles
❤️ Contributors
pnpm/pnpm
v7.29.1
Compare Source
Patch Changes
Our Gold Sponsors
Our Silver Sponsors
v7.29.0
Compare Source
Minor Changes
A new setting is now supported:
dedupe-peer-dependents
.When this setting is set to
true
, packages with peer dependencies will be deduplicated after peers resolution.For instance, let's say we have a workspace with two projects and both of them have
webpack
in their dependencies.webpack
hasesbuild
in its optional peer dependencies, and one of the projects hasesbuild
in its dependencies. In this case, pnpm will link two instances ofwebpack
to thenode_modules/.pnpm
directory: one withesbuild
and another one without it:This makes sense because
webpack
is used in two projects, and one of the projects doesn't haveesbuild
, so the two projects cannot share the same instance ofwebpack
. However, this is not what most developers expect, especially since in a hoistednode_modules
, there would only be one instance ofwebpack
. Therefore, you may now use thededupe-peer-dependents
setting to deduplicatewebpack
when it has no conflicting peer dependencies (explanation at the end). In this case, if we setdedupe-peer-dependents
totrue
, both projects will use the samewebpack
instance, which is the one that hasesbuild
resolved:What are conflicting peer dependencies? By conflicting peer dependencies we mean a scenario like the following one:
In this case, we cannot dedupe
webpack
aswebpack
hasreact
in its peer dependencies andreact
is resolved from two different versions in the context of the two projects.Patch Changes
The configuration added by
pnpm setup
should check if the pnpm home directory is already in the PATH before adding to the PATH.Before this change, this code was added to the shell:
Now this will be added:
Add
skipped
status in exec report summary when script is missing #6139.pnpm env -g
should fail with a meaningful error message if pnpm cannot find the pnpm home directory, which is the directory into which Node.js is installed.Should not throw an error when local dependency use file protocol #6115.
Fix the incorrect error block when subproject has been patched #6183
Our Gold Sponsors
Our Silver Sponsors
v7.28.0
Compare Source
Minor Changes
--report-summary
forpnpm exec
andpnpm run
#6008.pnpm why --json
or--long
#6103.pnpm.peerDependencyRules.allowedVersions
package.json
option to support theparent>child
selector syntax. This syntax allows for extending specificpeerDependencies
#6108.Patch Changes
peerDependenciesMeta
and notpeerDependencies
,dependencies
, oroptionalDependencies
, the dependency's peers were not considered deterministically before.patch-commit
should auto apply patches in workspaces #6048pnpm config set
should write to the global config file by default #5877.Our Gold Sponsors
Our Silver Sponsors
unjs/ufo
v1.1.1
Compare Source
compare changes
🩹 Fixes
✅ Tests
❤️ Contributors
Configuration
📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.