chore(deps): update all non-major dependencies #15
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.2
->^7.11.3
6.32.10
->6.32.24
^0.9.4
->^0.16.0
Release Notes
bcoe/c8
v7.11.3
Compare Source
pnpm/pnpm
v6.32.24
Compare Source
Patch 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:v6.32.23
Compare Source
Patch Changes
v6.32.22
Compare Source
Patch Changes
v6.32.21
Compare Source
Patch Changes
v6.32.20
Compare Source
Patch Changes
package.json
file #4822.v6.32.19
Compare Source
Patch Changes
v6.32.18
Compare Source
Patch Changes
auto-install-peers
is set totrue
#4796.NODE_ENV=production pnpm install --dev
should only install dev deps #4745.Full Changelog: pnpm/pnpm@v6.32.17...v6.32.18
v6.32.17
Compare Source
Patch Changes
v6.32.16
Compare Source
Patch Changes
auto-install-peers
is set totrue
, automatically install missing peer dependencies without writing them topackage.json
as dependencies. This makes pnpm handle peer dependencies the same way as npm v7 #4776.v6.32.15
Compare Source
Patch Changes
pnpm setup
should not fail on Windows ifPNPM_HOME
is not yet in the system registry #4757pnpm dlx
shouldn't modify the lockfile in the current working directory #4743.v6.32.14
Compare Source
Patch Changes
node_modules/.pnpm
and inside the global store #4716Full Changelog: pnpm/pnpm@v6.32.13...v6.32.14
v6.32.13
Compare Source
Patch Changes
pnpm setup
should update the config of the current shell, not the preferred shell.pnpm dlx
should work with git-hosted packages. For example:pnpm dlx gengjiawen/envinfo
#4714.pnpm setup
should not override the PNPM_HOME env variable on Windows, unless--force
is used.pnpm create <pkg>
should be passed to the executed create app package. Sopnpm create next-app --typescript
should work`.pnpm run --stream
should prefix the output with directory #4702Full Changelog: pnpm/pnpm@v6.32.12...v6.32.13
v6.32.12
Compare Source
Patch Changes
pnpm dlx
should work when the bin name of the executed package isn't the same as the package name #4672.pnpm prune
works in a workspace #4647.pnpm prune
does not remove hoisted dependencies.pnpm dlx
should print messages about installation to stderr #1698.v6.32.11
Compare Source
Patch Changes
pnpm publish
should work correctly in a workspace, when the latest npm CLI is installed #4348.node_modules/.ignored
subfolder and a package with that name is already present in `node_modules/.ignored' #4626.Full Changelog: pnpm/pnpm@v6.32.10...v6.32.11
vitest-dev/vitest
v0.16.0
Compare Source
🚨 Breaking Changes
#1525
by @sheremet-va🚀 Features
#1531
by @sheremet-va🐞 Bug Fixes
#1522
by @sheremet-va#1529
by @sheremet-va#1538
by @KentoMoriwakiView changes on GitHub
v0.15.2
Compare Source
🐞 Bug Fixes
#1496
#1431
#1503
#1511
#1505
#1510
#1506
❤️ Contributors
Thanks to @antfu | @nieyuyao | @RedJanvier | @renovate[bot] | @sheremet-va
View changes on GitHub
v0.15.1
Compare Source
🐞 Bug Fixes
css
option22fed1b8
❤️ Contributors
Thanks to @sheremet-va | @stormwarning
View changes on GitHub
v0.15.0
Compare Source
🚀 Features
#1468
VITEST_POOL_ID
#1473
maxConcurrency
option,5
by default#1483
#1477
css
config option, don't process CSS by default#1467
🐞 Bug Fixes
#1462
#1474
#1489
#1487
View changes on GitHub
v0.14.2
Compare Source
Bug Fixes
Features
--ouputDiffLines
cli flag (#1446) (0b8a5bc)v0.14.1
Compare Source
Bug Fixes
v0.14.0
Compare Source
Breaking Changes
.mjs
for esm build (692ad34)"type": "module"
from vitest/package.json (#1411) (b4a9b0b), closes #325watchIgnore
is renamed towatchExclude
and now accepts only glob patterns (#1424) (3f5ff5b)Bug Fixes
v0.13.1
Compare Source
Bug Fixes
Features
v0.13.0
Compare Source
Features
v0.12.10
Compare Source
Bug Fixes
Features
expect.extend
. (#1378) (4ec0a76)v0.12.9
Compare Source
Bug Fixes
v0.12.8
Compare Source
Bug Fixes
v0.12.7
Compare Source
Bug Fixes
Features
v0.12.6
Compare Source
Bug Fixes
.resolves
and.rejects
expectations (#1300) (789cc93)process.stdout
could be undefined on Windows (fix #1292) (#1305) (3179ac9)v0.12.5
Compare Source
Bug Fixes
Features
debug
(ed3374f)v0.12.4
Compare Source
Bug Fixes
Features
onConsoleLog
options to filter logs (35c1b52)f
to rerun only failed tests (#1283) (3c6f991)v0.12.3
Compare Source
Bug Fixes
v0.12.2
Compare Source
Bug Fixes
Features
v0.12.1
Compare Source
Bug Fixes
require
reference (5da8b00)Features
v0.12.0
Compare Source
Bug Fixes
Features
v0.11.0
Compare Source
Bug Fixes
src
(#1254) (b7973fe)Features
v0.10.5
Compare Source
Bug Fixes
Features
v0.10.4
Compare Source
Bug Fixes
v0.10.3
Compare Source
Bug Fixes
v0.10.2
Compare Source
Features
v0.10.1
Compare Source
Bug Fixes
Features
test.skipIf
andtest.runIf
apis (76c3894)v0.10.0
Compare Source
Breaking Changes
From Vitest v0.10.0, the callback style of declaring tests is deprecated. You can rewrite them to use
async
/await
functions, or use Promise to mimic the callback style.Features
beforeAll
/beforeEach
cleanup callbackbeforeAll
/beforeEach
now accepts an optional cleanup function as the return value (equivalent toafterAll
/afterEach
).Learn more at:
beforeAll
beforeEach
Test Context
Inspired by Playwright Fixtures, Vitest's test context allows you to define utils, states, and fixtures that can be used in your tests.
Learn more at Test Context
Concurrent Snapshot
Due to the limitation of JavaScript, timing based Singleton pattern will cause conflicts when running multiple async functions in concurrent. Previously reported as #551. Thanks to the newly introduced Test Context, we can now provide a test specific
expect
instance to avoid conflicts. To use it, you can destructure theexpect
from each test context instead of the global one.Reporter from file / package
Now you can pass a path to file, or a package name to the
reporters
options to use custom reporter. Thanks to @ericjgagnon (#1136) (f2bceb2)Bug Fixes
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.