Skip to content

chore(deps): update npm (major)#2019

Open
renovate[bot] wants to merge 1 commit into
developfrom
renovate/major-npm
Open

chore(deps): update npm (major)#2019
renovate[bot] wants to merge 1 commit into
developfrom
renovate/major-npm

Conversation

@renovate

@renovate renovate Bot commented Apr 12, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@​splunk/eslint-config ^5.0.0^6.0.0 age confidence
@types/react-dom (source) ^18.3.7^19.2.3 age confidence
@vitejs/plugin-react (source) ^4.7.0^6.0.2 age confidence
diff ^8.0.4^9.0.0 age confidence
http-proxy-middleware ^3.0.5^4.1.1 age confidence
typescript (source) ^5.9.3^6.0.3 age confidence
vite (source) ^7.3.1^8.0.16 age confidence
vite-plugin-dts (source) 4.5.35.0.2 age confidence

Release Notes

vitejs/vite-plugin-react (@​vitejs/plugin-react)

v6.0.2

Compare Source

Allow all options in reactCompilerPreset (#​1189)

This is a type only change. Only compilationMode and target options were available for reactCompilerPreset.

v6.0.1

Compare Source

Expand @rolldown/plugin-babel peer dep range (#​1146)

Expanded @rolldown/plugin-babel peer dep range to include ^0.2.0.

v6.0.0

Compare Source

v5.2.0

Compare Source

v5.1.4

Compare Source

Fix canSkipBabel not accounting for babel.overrides (#​1098)

When configuring babel.overrides without top-level plugins or presets, Babel was incorrectly skipped. The canSkipBabel function now checks for overrides.length to ensure override configurations are processed.

v5.1.3

Compare Source

v5.1.2

Compare Source

v5.1.1

Compare Source

Update code to support newer rolldown-vite (#​976)

rolldown-vite will remove optimizeDeps.rollupOptions in favor of optimizeDeps.rolldownOptions soon. This plugin now uses optimizeDeps.rolldownOptions to support newer rolldown-vite. Please update rolldown-vite to the latest version if you are using an older version.

v5.1.0

Compare Source

Add @vitejs/plugin-react/preamble virtual module for SSR HMR (#​890)

SSR applications can now initialize HMR runtime by importing @vitejs/plugin-react/preamble at the top of their client entry instead of manually calling transformIndexHtml. This simplifies SSR setup for applications that don't use the transformIndexHtml API.

Fix raw Rolldown support for Rolldown 1.0.0-beta.44+ (#​930)

Rolldown 1.0.0-beta.44+ removed the top-level jsx option in favor of transform.jsx. This plugin now uses the transform.jsx option to support Rolldown 1.0.0-beta.44+.

v5.0.4

Compare Source

Perf: use native refresh wrapper plugin in rolldown-vite (#​881)

v5.0.3

Compare Source

HMR did not work for components imported with queries with rolldown-vite (#​872)
Perf: simplify refresh wrapper generation (#​835)

v5.0.2

Compare Source

Skip transform hook completely in rolldown-vite in dev if possible (#​783)

v5.0.1

Compare Source

Set optimizeDeps.rollupOptions.transform.jsx instead of optimizeDeps.rollupOptions.jsx for rolldown-vite (#​735)

optimizeDeps.rollupOptions.jsx is going to be deprecated in favor of optimizeDeps.rollupOptions.transform.jsx.

Perf: skip babel-plugin-react-compiler if code has no "use memo" when { compilationMode: "annotation" } (#​734)
Respect tsconfig jsxImportSource (#​726)
Fix reactRefreshHost option on rolldown-vite (#​716)
Fix RefreshRuntime being injected twice for class components on rolldown-vite (#​708)
Skip babel-plugin-react-compiler on non client environment (689)

v5.0.0

Compare Source

kpdecker/jsdiff (diff)

v9.0.0

Compare Source

(All changes part of PR #​672.)

  • ES5 support is dropped. parsePatch now uses TextDecoder and Uint8Array, 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 diff and 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; parsePatch would 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, parsePatch parses all the possible escape sequences that GNU diff (or Git) ever output, and formatPatch quotes and escapes filenames containing special characters in the same way GNU diff does.

  • formatPatch now omits file headers when oldFileName or newFileName in the provided patch object are undefined, regardless of the headerOptions parameter. (Previously, it would treat the absence of oldFileName or newFileName as indicating the filename was the word "undefined" and emit headers --- undefined / +++ undefined.)

  • formatPatch no longer outputs trailing tab characters at the end of ---/+++ headers.

    Previously, if formatPatch was passed a patch object to serialize that had empty strings for the oldHeader or newHeader property, it would include a trailing tab character after the filename in the --- and/or +++ file header. Now, this scenario is treated the same as when oldHeader/newHeader is undefined - i.e. the trailing tab is omitted.

  • formatPatch no 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.) Previously formatPatch would provide the correct output but also mutate the oldLines or newLines property on the hunk, changing the meaning of the underlying patch.

  • Git-style patches are now supported by parsePatch, formatPatch, and reversePatch.

    Patches output by git diff can include some features that are unlike those output by GNU diff, 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 parsePatch parses 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 by parsePatch. See isGit and subsequent properties in the docs in the README.md file.

    formatPatch now outputs extended headers based on these new Git-specific properties, and reversePatch respects them as far as possible (with one unavoidable caveat noted in the README.md file).

  • Unpaired file headers now cause parsePatch to 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.

  • parsePatch is 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 +, -, or and 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 oldFileName and newFileName fields of StructuredPatch are now typed as string | undefined instead of string. This type change reflects the (pre-existing) reality that parsePatch can produce patches without filenames (e.g. when parsing a patch that simply contains hunks with no file headers).

chimurai/http-proxy-middleware (http-proxy-middleware)

v4.1.1

Compare Source

  • fix(fixRequestBody): harden form-data stringification

v4.1.0

Compare Source

  • feat(definePlugin): helper function to create plugins
  • chore(package.json): update to httpxy@​0.5.3
  • fix(ipv6): preserve credentials when normalizing bracketed IPv6 target string
  • fix(ipv6): unspecified IPv6 target hostname (::)
  • fix(response-interceptor): reduce responseInterceptor buffer churn
  • fix(ws): handle multi-server upgrade subscription and safe proxy shutdown
  • feat(router): add 'res' and 'options' to router function
  • feat(pathRewrite): add 'res' and 'options' to custom pathRewrite function
  • fix(responseInterceptor): prevent trailer/content-length conflict
  • feat(zstd): support zstd compression in responseInterceptor and fixRequestBody
  • fix(responseInterceptor): handle bodyless responses (HEAD/1xx/204/304) with content-encoding
  • fix(router): harden proxy-table matching

v4.0.0

Compare Source

  • fix(types): fix Logger type
  • fix(error-response-plugin): sanitize input
  • feat: drop node v14/v16/v18 [BREAKING CHANGE]
  • refactor: replace http-proxy w/ httpxy
  • chore: remove legacyCreateProxyMiddleware() [BREAKING CHANGE]
  • ci: migrate from jest to vitest
  • chore(package.json): esm only [BREAKING CHANGE]
  • chore(package.json): bump to httpxy 0.5.0 (#​1183)
  • chore(package.json): drop node20 [BREAKING CHANGE] (#​1179)
  • refactor: remove deprecated url.parse() (#​1176)
  • fix(fixRequestBody): support content-encoding on request body (#​1142)
  • fix: prevent TypeError when ws enabled but server is undefined (#​1163)
  • fix: applyPathRewrite logs old req.url instead of rewritten path (#​1157)
  • feat(hono): support for hono with createHonoProxyMiddleware
  • feat(ipv6): support literal IPv6 addresses in target and forward options (ie. "http://[::1]:8000")
  • chore(package.json): bump httpxy to ^0.5.1
  • fix(logger-plugin): support ipv6 host and handle undefined protocol/host
  • ci(publish.yml): pin github.triggering_actor
  • chore(package.json): node ^22.15.0 (#​1218)
  • refactor(package): subpath 'http-proxy-middleware/hono' (#​1220)
  • chore: node 26 support

v3.0.7

Compare Source

What's Changed

Full Changelog: chimurai/http-proxy-middleware@v3.0.6...v3.0.7

v3.0.6

Compare Source

What's Changed

New Contributors

Full Changelog: chimurai/http-proxy-middleware@v3.0.5...v3.0.6

microsoft/TypeScript (typescript)

v6.0.3

Compare Source

v6.0.2

Compare Source

vitejs/vite (vite)

v8.0.16

Compare Source

Bug Fixes

v8.0.15

Compare Source

Features
Bug Fixes
  • capitalize error messages and remove spurious space in parse error (#​22488) (85a0eff)
  • deps: update all non-major dependencies (#​22511) (2686d7d)
  • dev: fix html-proxy cache key mismatch for /@​fs/ HTML paths (#​21762) (47c4213)
  • glob: error on relative glob in virtual module when no files match (#​22497) (5c8e98f)
  • optimizer: close the rolldown bundle when write() rejects (#​22528) (e3cfb9d)
  • resolve: provide onWarn for viteResolvePlugin in JS plugin containers (#​22509) (40985f1)
Miscellaneous Chores
Code Refactoring

v8.0.14

Compare Source

Features
Bug Fixes
Miscellaneous Chores
  • deps: update rolldown-related dependencies (#​22470) (7cb728e)
  • remove irrelevant commits from changelog (2c69495)
Code Refactoring
Tests

v8.0.13

Compare Source

Features
Bug Fixes
Miscellaneous Chores

v8.0.12

Compare Source

Features
Bug Fixes
  • create-vite: pass react framework to TanStack CLI (#​22397) (18f0f90)
  • deps: update all non-major dependencies (#​22420) (2be6000)
  • module-runner: prevent partial-exports race on concurrent imports of in-flight invalidated re-export chains (#​22369) (f5a22e6)
  • refer to rolldownOptions instead of deprecated rollupOptions in messages (#​22400) (b675c7b)
  • worker: apply build.target to worker bundle (#​22404) (3c93fde)
  • worker: forward define to worker bundle transform (#​22408) (d4838a0)
Miscellaneous Chores

v8.0.11

Compare Source

Features
Bug Fixes
Documentation
Miscellaneous Chores
Code Refactoring
Tests

v8.0.10

Compare Source

Features
Bug Fixes
  • hmrClient.logger.debug and hmrClient.logger.error looked different from other HMR logs (#​22147) (a4d828f)
  • css: show filename in CSS minification warnings for .css?inline (#​22292) (83f0a78)
  • optimizer: allow user transform.target to override default in optimizeDeps (#​22273) (5c7cec6)
  • remove format sniffing module resolution from JS resolver (#​22297) (b8a21cc)
Code Refactoring

v8.0.9

Compare Source

Features
Bug Fixes
Documentation
Miscellaneous Chores

v8.0.8

Compare Source

Features
Bug Fixes

v8.0.7

Compare Source

Bug Fixes
  • use sync dns.getDefaultResultOrder instead of dns.promises (#​22185) (5c05b04)

v8.0.6

Compare Source

Features
Bug Fixes
Performance Improvements
  • early return in getLocalhostAddressIfDiffersFromDNS when DNS order is verbatim (#​22151) (56ec256)
Miscellaneous Chores

v8.0.5

Compare Source

Bug Fixes

v8.0.4

Compare Source

Features
Bug Fixes
Documentation

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every 2 weeks on Sunday"
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested a review from a team as a code owner April 12, 2026 06:10
@renovate renovate Bot requested a review from soleksy-splunk April 12, 2026 06:10
@renovate renovate Bot force-pushed the renovate/major-npm branch 5 times, most recently from 7ae2a39 to 49c22b3 Compare April 19, 2026 18:31
@renovate renovate Bot force-pushed the renovate/major-npm branch 3 times, most recently from 3b48a4d to c6d3e7f Compare April 22, 2026 20:13
@pull-request-size pull-request-size Bot added size/L and removed size/M labels Apr 22, 2026
@renovate renovate Bot force-pushed the renovate/major-npm branch 10 times, most recently from 65c1269 to 7ec4621 Compare April 24, 2026 15:02
@renovate renovate Bot force-pushed the renovate/major-npm branch from 7ec4621 to 21489fb Compare April 30, 2026 13:00
@renovate renovate Bot force-pushed the renovate/major-npm branch 3 times, most recently from 0cb58cc to 917a262 Compare May 11, 2026 11:38
@renovate renovate Bot force-pushed the renovate/major-npm branch from 917a262 to 99d4e1c Compare May 14, 2026 14:53
@renovate renovate Bot force-pushed the renovate/major-npm branch 4 times, most recently from fe4956e to 08ec504 Compare May 21, 2026 12:07
@renovate renovate Bot force-pushed the renovate/major-npm branch 6 times, most recently from 19935a8 to f3d9748 Compare June 6, 2026 18:47
@renovate renovate Bot force-pushed the renovate/major-npm branch 5 times, most recently from 9f04867 to cde34a9 Compare June 12, 2026 10:15
@renovate renovate Bot force-pushed the renovate/major-npm branch from cde34a9 to dec9f81 Compare June 14, 2026 22:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants