chore(deps): update npm-rolldown (major)#1863
Merged
IWANABETHATGUY merged 2 commits intomainfrom Aug 13, 2024
Merged
Conversation
✅ Deploy Preview for rolldown-rs canceled.
|
7d860e8 to
c681feb
Compare
IWANABETHATGUY
pushed a commit
that referenced
this pull request
Aug 11, 2024
### Description - base branch #1863 Vitest v2 update is failing in #1863, but accompanying it with vite v5.4 should fix it (see Vite PR for details vitejs/vite#17807).
413767e to
8ddb0c3
Compare
IWANABETHATGUY
approved these changes
Aug 13, 2024
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
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:
20.14.15->22.2.0^10.4.1->^11.0.0^1.6.0->^2.0.0^2.2.2->^3.0.0Release Notes
isaacs/node-glob (glob)
v11.0.0Compare Source
vitest-dev/vitest (vitest)
v2.0.5Compare Source
🚀 Features
🐞 Bug Fixes
testNamePatternadds leading space - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6186 (073a5)afterEachcleanup hooks in node entrypoint - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6192 (e6fbc)defineProjectanddefineWorkspacetypes - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6198 (8cd82)node:*imports in__mocks__folder - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6204 (a48be)View changes on GitHub
v2.0.4Compare Source
🐞 Bug Fixes
require- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6159 (807a2)*.ctsfiles - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6189 (5da45)thresholds.<glob>.100option - by @thor-juhasz and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6174 (f6845)mockImplementationfor function overload and unions - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6181 (7a75b)View changes on GitHub
v2.0.3Compare Source
🚀 Features
🐞 Bug Fixes
--inspect-brkstop on Windows - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6110 (f8519)vi.spyOntoMockInstanceof function overload - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/6086 (e9f9a)View changes on GitHub
v2.0.2Compare Source
v2.0.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.0.0Compare Source
Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.
🚨 Breaking Changes
--segfault-retry- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5514 (ed60e)threadssegfaults. Our current recommendation is to use the new defaultforkspool instead.onTestFinishedhook. This can make your tests run a little bit slower.coverage.ignoreEmptyLinesby default - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5543 (31994)locationfield pointed to the error location instead of the test location. Now it is aligned with jest and contains thelineandcolumnof a test function, but requiresincludeTaskLocationto be enabled.poolto'forks'- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5047 (7f8f9)threadspool: https://vitest.dev/guide/improving-performance.html#pool--merge-reportsto support coverage - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5736 (b7438)spy.mock.returns. If the function is async or returns a promise, it will always succeed and have aPromiseinresults. To make migration easier, we introducedspy.mock.settledResultsthat unwraps promises andexpect().toHaveResolved()matcher that accepts unwrapped value.jsonoutput - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5802 (dd754)indexScriptstoorchestratorScriptsin the browser config - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5842 (49f34)poolAPI - now requirescollectTestsmethod alongsiderunTests.🚀 Features
--output-json- by @Joristdh in https://github.com/vitest-dev/vitest/issues/5745 (0766b)parseAst,parseAstAsyncfrom vite - by @sheremet-va (f645e)clickevent - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5777 (839c3)page.screenshotmethod - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5853 (81c42)userEventmethods, addfillanddragAndDropevents - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5882 (4dbea)expect.dommethod and bundlejest-dommatchers with@vitest/browser- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5910 (3a96a)tripleClickto interactive api - by @userquin in https://github.com/vitest-dev/vitest/issues/5987 (200a4)test.for- by @hi-ogawa and @sheremet-va in https://github.com/vitest-dev/vitest/issues/5861 (c2380)🐞 Bug Fixes
--excludeoption - by @fregante in https://github.com/vitest-dev/vitest/issues/5782 (d6700)project.providetype - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5959 (0eda9)previewprovider when running in StackBlitz - by @userquin in https://github.com/vitest-dev/vitest/issues/5836 (76e13)coverage.reporterfrom string values - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5920 (f33da)thresholds.autoUpdateto supportmergeConfig- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5818 (7afb3)stderrofstartVitest()- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5954 (70805)exclude- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5997 (169bc)else- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/6014 (368c1)test-excludeto v7 - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5867 (0a715)poolOptions.<name>.isolatefromforksoptions - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/5840 (a60a1)toMatchFileSnapshotwith empty file - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/5894 (88006)FileDetailstitle status icon not being updated - by @userquin in https://github.com/vitest-dev/vitest/issues/5942 (e9ddf)VITE_- by @sheremet-va in https://github.com/vitest-dev/vitest/issues/6017 (d87be)provideto the public API - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/5897 (66e64)View changes on GitHub
mafintosh/why-is-node-running (why-is-node-running)
v3.2.0Compare Source
Notable Changes
Relative file paths
The file paths shown in the output are now relative to the current working directory, if a path is outside of the current working directory the full absolute path will be used instead.
Before
After
No more dependencies
This version of
why-is-node-runningremoves all of it's additional dependencies, resulting in a smaller overall package size.What's Changed
filesfield topackage.jsonby @jonkoops in https://github.com/mafintosh/why-is-node-running/pull/76siginfopackage by @jonkoops in https://github.com/mafintosh/why-is-node-running/pull/77stackbackwith internal implementation by @jonkoops in https://github.com/mafintosh/why-is-node-running/pull/80Full Changelog: mafintosh/why-is-node-running@v3.1.0...v3.2.0
v3.1.0Compare Source
What's Changed
includeentrypoint by @jonkoops in https://github.com/mafintosh/why-is-node-running/pull/71npxby @jonkoops in https://github.com/mafintosh/why-is-node-running/pull/66Full Changelog: mafintosh/why-is-node-running@v3.0.0...v3.1.0
v3.0.0Compare Source
What's Changed
Breaking Changes
This release raises the required Node.js version to 20.11 or higher, and introduces support for standardized JavaScript modules. This makes the package incompatible with CommonJS based environments and is thus a breaking change. If you want to use this version the following changes should be made:
Use JavaScript modules instead of CommonJS
Use
--importinstead of--requireFull Changelog: mafintosh/why-is-node-running@v2.3.0...v3.0.0
Configuration
📅 Schedule: Branch creation - "before 10am on monday" in timezone Asia/Shanghai, 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 was generated by Mend Renovate. View the repository job log.