chore(deps): update all non-major dependencies #38
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:
^7.11.0
->^7.12.0
7.3.0
->7.9.0
^0.9.2
->^0.21.0
Release Notes
bcoe/c8
v7.12.0
Compare Source
Features
7.11.3 (2022-05-16)
Bug Fixes
--all
now respects--extension
flag. (#357) (a5deb27)7.11.2 (2022-04-20)
Bug Fixes
this.exclude.shouldInstrument
for improved performance (#388) (8b36f23)7.11.1 (2022-04-20)
Bug Fixes
test:snap
script to use cross-env (#366) (5d2981c)v7.11.3
Compare Source
v7.11.2
Compare Source
v7.11.1
Compare Source
pnpm/pnpm
v7.9.0
Compare Source
Minor Changes
ignore-dep-scripts
istrue
, ignore scripts of dependencies but run the scripts of the project.ignore-compatibility-db
is set totrue
, the compatibility database will not be used to patch dependencies #5132.Patch Changes
pnpm setup
should suggest users to source the config instead of restarting the terminal.bin
that points to an.exe
file on Windows #5159.verify-store-integrity
is set tofalse
.Our Gold Sponsors
v7.8.0
Compare Source
Minor Changes
publishConfig.directory
is set, only symlink it to other workspace projects ifpublishConfig.linkDirectory
is set totrue
. Otherwise, only use it for publishing #5115.Patch Changes
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.7.1...v7.8.0
v7.7.1
Compare Source
Patch Changes
auto-install-peers
is set totrue
and the peer dependency is indevDependencies
oroptionalDependencies
#5080.workspace:^
orworkspace:~
version specs are used in a workspace.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.7.0...v7.7.1
v7.7.0
Compare Source
Minor Changes
Add experimental lockfile format that should merge conflict less in the
importers
section. Enabled by setting theuse-inline-specifiers-lockfile-format = true
feature flag in.npmrc
.If this feature flag is committed to a repo, we recommend setting the minimum allowed version of pnpm to this release in the
package.json
engines
field. Once this is set, older pnpm versions will throw on invalid lockfile versions.Add
publishDirectory
field to the lockfile and relink the project when it changes.verify-store-integrity=false
makes pnpm skip checking the integrities of files in the global content-addressable store.Allow to set
only-built-dependencies[]
through.npmrc
.Patch Changes
publishConfig.directory
) #3901.pnpm deploy
should inject local dependencies of all types (dependencies, optionalDependencies, devDependencies) #5078.publishConfig.directory
set, dependent projects should install the project from that directory #3901.zshrc
in the right directory when a$ZDOTDIR
is set.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.6.0...v7.7.0
v7.6.0
Compare Source
Minor Changes
A new setting supported:
prefer-symlinked-executables
. Whentrue
, pnpm will create symlinks to executables innode_modules/.bin
instead of command shims (but on POSIX systems only).This setting is
true
by default whennode-linker
is set tohoisted
.Related issue: #4782.
When
lockfile-include-tarball-url
is set totrue
, every entry inpnpm-lock.yaml
will contain the full URL to the package's tarball #5054.Patch Changes
pnpm deploy
should include all dependencies by default #5035.Don't print warnings about file verifications. Just print info messages instead.
pnpm publish --help
should print the--recursive
and--filter
options #5019.It should be possible to run exec/run/dlx with the
--use-node-version
option.pnpm deploy
should not modify the lockfile #5071pnpm deploy
should not fail in CI #5071When
auto-install-peers
is set totrue
, automatically install direct peer dependencies #5028.So if your project the next manifest:
pnpm will install both lodash and react as a regular dependencies.
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.5.2...v7.6.0
v7.5.2
Compare Source
Patch Changes
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.5.1...v7.5.2
v7.5.1
Compare Source
Patch Changes
node_modules
#4988.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.5.0...v7.5.1
v7.5.0
Compare Source
Minor Changes
A new value
rolling
for optionsave-workspace-protocol
. When selected, pnpm will save workspace versions using a rolling alias (e.g."foo": "workspace:^"
) instead of pinning the current version number (e.g."foo": "workspace:^1.0.0"
). Usage example, in the root of your workspace, create a.npmrc
with the following content:Patch Changes
pnpm remove <pkg>
should not fail in a workspace that has patches #4954pnpm env use
should throw an error on a system that use the MUSL libc.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.4.1...v7.5.0
v7.4.1
Compare Source
Patch Changes
pnpm install
in a workspace with patches should not fail when doing partial installation #4954.--lockfile-only
is used. Even iffrozen-lockfile
istrue
#4951.patchedDependencies
field topnpm-lock.yaml
.Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.4.0...v7.4.1
v7.4.0
Compare Source
Minor Changes
Dependencies patching is possible via the
pnpm.patchedDependencies
field of thepackage.json
.To patch a package, the package name, exact version, and the relative path to the patch file should be specified. For instance:
Two new commands added:
pnpm patch
andpnpm patch-commit
.pnpm patch <pkg>
prepares a package for patching. For instance, if you want to patch express v1, run:pnpm will create a temporary directory with
express@1.0.0
that you can modify with your changes.Once you are read with your changes, run:
This will create a patch file and write it to
<project>/patches/express@1.0.0.patch
.Also, it will reference this new patch file from the
patchedDependencies
field inpackage.json
:A new experimental command added:
pnpm deploy
. The deploy command takes copies a project from a workspace and installs all of its production dependencies (even if some of those dependencies are other projects from the workspace).For example, the new command will deploy the project named
foo
to thedist
directory in the root of the workspace:package-import-method
supports a new option:clone-or-copy
.New setting added:
include-workspace-root
. When it is set totrue
, therun
,exec
,add
, andtest
commands will include the root package, when executed recursively #4906Patch Changes
Don't crash when
pnpm update --interactive
is cancelled with Ctrl+c.The
use-node-version
setting should work with prerelease Node.js versions. For instance:Return early when the lockfile is up-to-date.
Resolve native workspace path for case-insensitive file systems #4904.
Don't link local dev dependencies, when prod dependencies should only be installed.
pnpm audit --fix
should not add an override for a vulnerable package that has no fixes released.Update the compatibility database.
Our Gold Sponsors
Full Changelog: pnpm/pnpm@v7.3.0...v7.4.0
vitest-dev/vitest
v0.21.0
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.20.3
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.20.2
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.20.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.20.0
Compare Source
🚨 Breaking Changes
🚀 Features
🐞 Bug Fixes
clover
reporter by default - by @antfu (5862e)View changes on GitHub
v0.19.1
Compare Source
🚀 Features
View changes on GitHub
v0.19.0
Compare Source
🚨 Breaking Changes
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.18.1
Compare Source
🚀 Features
/es/...
and/lib/...
- by @zthxxx in https://github.com/vitest-dev/vitest/issues/1633🐞 Bug Fixes
test.each
anddescribe.each
types - by @Demivan in https://github.com/vitest-dev/vitest/issues/1653View changes on GitHub
v0.18.0
Compare Source
🚨 Breaking Changes
ctx.log
toctx.logger.log
, improve log flicking - by @userquin and @antfu in https://github.com/vitest-dev/vitest/issues/1166🐞 Bug Fixes
ctx.cache
- by @antfu (695a7)View changes on GitHub
v0.17.1
Compare Source
🚀 Features
forceRerunTriggers
- by @elliotwestlake and @sheremet-va in https://github.com/vitest-dev/vitest/issues/1595🐞 Bug Fixes
View changes on GitHub
v0.17.0
Compare Source
🚀 Features
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.
👻 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.