chore(deps): update npm (major)#2019
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/major-npm
branch
5 times, most recently
from
April 19, 2026 18:31
7ae2a39 to
49c22b3
Compare
renovate
Bot
force-pushed
the
renovate/major-npm
branch
3 times, most recently
from
April 22, 2026 20:13
3b48a4d to
c6d3e7f
Compare
renovate
Bot
force-pushed
the
renovate/major-npm
branch
10 times, most recently
from
April 24, 2026 15:02
65c1269 to
7ec4621
Compare
renovate
Bot
force-pushed
the
renovate/major-npm
branch
from
April 30, 2026 13:00
7ec4621 to
21489fb
Compare
renovate
Bot
force-pushed
the
renovate/major-npm
branch
3 times, most recently
from
May 11, 2026 11:38
0cb58cc to
917a262
Compare
renovate
Bot
force-pushed
the
renovate/major-npm
branch
from
May 14, 2026 14:53
917a262 to
99d4e1c
Compare
renovate
Bot
force-pushed
the
renovate/major-npm
branch
7 times, most recently
from
June 16, 2026 14:58
289ae57 to
7d6359d
Compare
renovate
Bot
force-pushed
the
renovate/major-npm
branch
8 times, most recently
from
June 24, 2026 09:00
b97bdad to
2b6cd4f
Compare
renovate
Bot
force-pushed
the
renovate/major-npm
branch
12 times, most recently
from
July 1, 2026 08:05
856e828 to
279a161
Compare
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:
^7.29.0→^8.0.1^7.28.6→^8.0.1^7.28.6→^8.0.1^7.29.0→^8.0.1^7.29.2→^8.0.2^7.28.5→^8.0.1^5.0.0→^6.0.0^3.2.0→^4.0.0^18.3.7→^19.2.3^4.7.0→^6.0.3^8.0.4→^9.0.0^3.1.2→^4.1.1^3.0.5→^4.2.0^4.1.1→^5.2.1^5.9.3→^7.0.2^7.3.1→^8.1.54.5.3→5.0.3Release Notes
babel/babel (@babel/core)
v8.0.1Compare Source
💥 Breaking Change
babel-core,babel-plugin-transform-object-rest-spread,babel-plugin-transform-runtime,babel-preset-env,babel-standalonepreset-env'suseBuiltIns(@nicolo-ribaudo)v8.0.0Compare Source
👓 Spec Compliance
babel-core💥 Breaking Change
babel-cli,babel-node,babel-plugin-proposal-decorators,babel-plugin-transform-classes,babel-plugin-transform-function-name,babel-plugin-transform-modules-commonjs,babel-plugin-transform-object-rest-spread,babel-plugin-transform-parameters,babel-plugin-transform-react-constant-elements,babel-plugin-transform-regenerator,babel-preset-env,babel-registermodules: auto(@nicolo-ribaudo)babel-plugin-transform-runtime,babel-runtime-corejs3,babel-runtime@babe/runtime-corejs3(@liuxingbaoyu)babel-parserlocations: "packed"(@liuxingbaoyu)🐛 Bug Fix
babel-generatorbabel-plugin-transform-modules-systemjs📝 Documentation
🏠 Internal
🏃♀️ Performance
babel-corevitejs/vite-plugin-react (@vitejs/plugin-react)
v6.0.3Compare Source
v6.0.2Compare Source
Allow all options in reactCompilerPreset (#1189)
This is a type only change. Only
compilationModeandtargetoptions were available forreactCompilerPreset.v6.0.1Compare Source
Expand
@rolldown/plugin-babelpeer dep range (#1146)Expanded
@rolldown/plugin-babelpeer dep range to include^0.2.0.v6.0.0Compare Source
v5.2.0Compare Source
v5.1.4Compare Source
Fix
canSkipBabelnot accounting forbabel.overrides(#1098)When configuring
babel.overrideswithout top-level plugins or presets, Babel was incorrectly skipped. ThecanSkipBabelfunction now checks foroverrides.lengthto ensure override configurations are processed.v5.1.3Compare Source
v5.1.2Compare Source
v5.1.1Compare Source
Update code to support newer
rolldown-vite(#976)rolldown-vitewill removeoptimizeDeps.rollupOptionsin favor ofoptimizeDeps.rolldownOptionssoon. This plugin now usesoptimizeDeps.rolldownOptionsto support newerrolldown-vite. Please updaterolldown-viteto the latest version if you are using an older version.v5.1.0Compare Source
Add
@vitejs/plugin-react/preamblevirtual module for SSR HMR (#890)SSR applications can now initialize HMR runtime by importing
@vitejs/plugin-react/preambleat the top of their client entry instead of manually callingtransformIndexHtml. This simplifies SSR setup for applications that don't use thetransformIndexHtmlAPI.Fix raw Rolldown support for Rolldown 1.0.0-beta.44+ (#930)
Rolldown 1.0.0-beta.44+ removed the top-level
jsxoption in favor oftransform.jsx. This plugin now uses thetransform.jsxoption to support Rolldown 1.0.0-beta.44+.v5.0.4Compare Source
Perf: use native refresh wrapper plugin in rolldown-vite (#881)
v5.0.3Compare Source
HMR did not work for components imported with queries with rolldown-vite (#872)
Perf: simplify refresh wrapper generation (#835)
v5.0.2Compare Source
Skip transform hook completely in rolldown-vite in dev if possible (#783)
v5.0.1Compare Source
Set
optimizeDeps.rollupOptions.transform.jsxinstead ofoptimizeDeps.rollupOptions.jsxfor rolldown-vite (#735)optimizeDeps.rollupOptions.jsxis going to be deprecated in favor ofoptimizeDeps.rollupOptions.transform.jsx.Perf: skip
babel-plugin-react-compilerif code has no"use memo"when{ compilationMode: "annotation" }(#734)Respect tsconfig
jsxImportSource(#726)Fix
reactRefreshHostoption on rolldown-vite (#716)Fix
RefreshRuntimebeing injected twice for class components on rolldown-vite (#708)Skip
babel-plugin-react-compileron non client environment (689)v5.0.0Compare Source
kpdecker/jsdiff (diff)
v9.0.0Compare Source
(All changes part of PR #672.)
ES5 support is dropped.
parsePatchnow usesTextDecoderandUint8Array, which are not available in ES5, and TypeScript is now compiled with the "es6"target. From now on, I intend to freely use any features that are deemed "Widely available" by Baseline. Users who need ES5 support should stick to version 8.C-style quoted strings in filename headers are now properly supported.
When the name of either the old or new file in a patch contains "special characters", both GNU
diffand Git quote the filename in the patch's headers and escape special characters using the same escape sequences that are used in string literals in C, including octal escapes for all non-ASCII characters. Previously, jsdiff had very little support for this;parsePatchwould remove the quotes, and unescape any escaped backslashes, but would not unescape other escape sequences.formatPatch, meanwhile, did not quote or escape special characters at all.Now,
parsePatchparses all the possible escape sequences that GNU diff (or Git) ever output, andformatPatchquotes and escapes filenames containing special characters in the same way GNU diff does.formatPatchnow omits file headers whenoldFileNameornewFileNamein the provided patch object areundefined, regardless of theheaderOptionsparameter. (Previously, it would treat the absence ofoldFileNameornewFileNameas indicating the filename was the word "undefined" and emit headers--- undefined/+++ undefined.)formatPatchno longer outputs trailing tab characters at the end of---/+++headers.Previously, if
formatPatchwas passed a patch object to serialize that had empty strings for theoldHeaderornewHeaderproperty, it would include a trailing tab character after the filename in the---and/or+++file header. Now, this scenario is treated the same as whenoldHeader/newHeaderisundefined- i.e. the trailing tab is omitted.formatPatchno longer mutates its input when serializing a patch containing a hunk where either the old or new content contained zero lines. (Such a hunk occurs only when the hunk has no context lines and represents a pure insertion or pure deletion, which for instance will occur whenever one of the two files being diffed is completely empty.) PreviouslyformatPatchwould provide the correct output but also mutate theoldLinesornewLinesproperty on the hunk, changing the meaning of the underlying patch.Git-style patches are now supported by
parsePatch,formatPatch, andreversePatch.Patches output by
git diffcan include some features that are unlike those output by GNUdiff, and therefore not handled by an ordinary unified diff format parser. An ordinary diff simply describes the differences between the content of two files, but Git diffs can also indicate, via "extended headers", the creation or deletion of (potentially empty) files, indicate that a file was renamed, and contain information about file mode changes. Furthermore, when these changes appear in a diff in the absence of a content change (e.g. when an empty file is created, or a file is renamed without content changes), the patch will contain no associated---/+++file headers nor any hunks.jsdiff previously did not support parsing Git's extended headers, nor hunkless patches. Now
parsePatchparses some of the extended headers, parses hunkless Git patches, and can determine filenames (e.g. from the extended headers) when parsing a patch that includes no---or+++file headers. The additional information conveyed by the extended headers we support is recorded on new fields on the result object returned byparsePatch. SeeisGitand subsequent properties in the docs in the README.md file.formatPatchnow outputs extended headers based on these new Git-specific properties, andreversePatchrespects them as far as possible (with one unavoidable caveat noted in the README.md file).Unpaired file headers now cause
parsePatchto throw.It remains acceptable to have a patch with no file headers whatsoever (e.g. one that begins with a
@@​hunk header on the very first line), but a patch with only a---header or only a+++header is now considered an error.parsePatchis now more tolerant of "trailing garbage"That is: after a patch, or between files/indexes in a patch, it is now acceptable to have arbitrary lines of "garbage" (so long as they unambiguously have no syntactic meaning - e.g. trailing garbage that leads with a
+,-, orand thus is interpretable as part of a hunk still triggers a throw).This means we no longer reject patches output by tools that include extra data in "garbage" lines not understood by generic unified diff parsers. (For example, SVN patches can include "Property changes on:" lines that generic unified diff parsers should discard as garbage; jsdiff previously threw errors when encountering them.)
This change brings jsdiff's behaviour more in line with GNU
patch, which is highly permissive of "garbage".The
oldFileNameandnewFileNamefields ofStructuredPatchare now typed asstring | undefinedinstead ofstring. This type change reflects the (pre-existing) reality thatparsePatchcan produce patches without filenames (e.g. when parsing a patch that simply contains hunks with no file headers).fastify/fast-uri (fast-uri)
v4.1.1Compare Source
Fix for GHSA-v2hh-gcrm-f6hx
Full Changelog: fastify/fast-uri@v4.1.0...v4.1.1
v4.1.0Compare Source
v4.0.1Compare Source
What's Changed
New Contributors
Full Changelog: fastify/fast-uri@v4.0.0...v4.0.1
v4.0.0Compare Source
What's Changed
Full Changelog: fastify/fast-uri@v3.1.2...v4.0.0
v3.1.4Compare Source
Fix for GHSA-v2hh-gcrm-f6hx
Full Changelog: fastify/fast-uri@v3.1.3...v3.1.4
v3.1.3Compare Source
Full Changelog: fastify/fast-uri@v3.1.2...v3.1.3
chimurai/http-proxy-middleware (http-proxy-middleware)
v4.2.0Compare Source
v4.1.1Compare Source
v4.1.0Compare Source
v4.0.0Compare Source
targetandforwardoptions (ie. "http://[::1]:8000")nodeca/js-yaml (js-yaml)
v5.2.1Compare Source
Fixed
Mapsupport to !!omap (should work whenrealMapTagused)Security
addItem. Regression from v5(usually not critical, because YAML11_SCHEMA is not default anymore).
v5.2.0Compare Source
Added
maxTotalMergeKeys(10000) loader option to limit the total number ofkeys processed by YAML merge (
<<) across oneload()/loadAll()call.maxAliases(-1) loader option to limit the number of YAML aliases perdocument.
Removed
maxMergeSeqLengthreplaced withmaxTotalMergeKeysfor limiting YAML mergeprocessing.
Fixed
1e21)v5.1.0Compare Source
Added
different result value.
Changed
quoteStylenow selects the preferred quote style; use therestored
forceQuotesoption to force quoting non-key strings.v5.0.0Compare Source
Added
JSON_SCHEMAandCORE_SCHEMAwith spec-compliant scalar resolutionrules, and added
YAML11_SCHEMA.realMapTagfor lossless mappings with non-string and complex keys.Object-based mappings now reject complex keys instead of stringifying them.
dump()transformoption for changing the generated AST beforerendering.
dump()optionsseqInlineFirst,flowBracketPadding,flowSkipCommaSpace,flowSkipColonSpace,quoteFlowKeys,quoteStyleandtagBeforeAnchor.test set.
Changed
exports.
CORE_SCHEMA(loader default),JSON_SCHEMA,FAILSAFE_SCHEMA.YAML11_SCHEMA, a combination of all YAML 1.1 tags (YAML 1.1 does notspecify a schema, only "types").
load/dumpdefault behaviour is now specified exactly via schemas:loadusesCORE_SCHEMA, without!!mergeby default.dumpusesYAML11_SCHEMA+CORE_SCHEMAfor the quoting check, toguarantee backward compatibility by default.
!!setis now loaded as a JavaScriptSet.TypeAPI with a tags API. Similar, but more precise andsimpler. See examples for details. Tags can be defined via
defineScalarTag(),defineSequenceTag()anddefineMappingTag(), or as aspread + override of an existing tag.
Schema.extend()toSchema.withTags().markers, block keys, multiline scalars, tag syntax and other things.
load()now throws on empty input instead of returningundefined.js-yaml/browserexport.loadAllsignature with an iterator (still works, but is acandidate for removal).
Removed
safeLoad(),safeLoadAll()andsafeDump()exports.DEFAULT_SCHEMAand the nestedtypesexport.onWarning,legacyandlistener.styles,replacer,noCompatMode,condenseFlow,quotingTypeandforceQuotes. RenamednoArrayIndenttoseqNoIndent.Formatting and representation are now configured through presenter options,
schemas and tag definitions. See migration guide on how to replace.
lib/.microsoft/TypeScript (typescript)
v7.0.2Compare Source
v6.0.3: TypeScript 6.0.3Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
v6.0.2: TypeScript 6.0Compare Source
For release notes, check out the release announcement blog post.
Downloads are available on:
vitejs/vite (vite)
v8.1.5Compare Source
Please refer to CHANGELOG.md for details.
v8.1.4Compare Source
Features
Bug Fixes
import.meta.urlin preload function as-is (#22839) (f1f90ed)Documentation
@defaultforserver.cors(#22859) (70435b2)Miscellaneous Chores
Code Refactoring
Tests
Build System
onwarnwithonLog(#22741) (c581b55)v8.1.3Compare Source
Bug Fixes
es-module-lexerto 2.3.0 (#22838) (7103c3a)v8.1.2Compare Source
Bug Fixes
v8.1.1Compare Source
Features
Bug Fixes
import.meta.hot.invalidate()(#22797) (709eb8e)@importurls with lightningcss (#22718) (9fa7ab4)esbuild.jsxSideEffectswhen converting tooxc.jsx.pure(#22809) (33895ba)ERR_CLOSED_SERVERin scanner (#22784) (085a0ab)inputfromroot(#22769) (9722b07)Miscellaneous Chores
Code Refactoring
Object.valuescalls (#22790) (1113acf)Tests
v8.1.0Compare Source
Features
server.fs.denylist with common files (#22707) (61ba8fd)~for Rolldown (#22693) (9928722)Bug Fixes
Code Refactoring
rolldownOptionsproperty for chunkImportMap (#22692) (8e8816c)v8.0.16Compare Source
Bug Fixes
v8.0.15Compare Source
Features
Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.