Bump the npm_and_yarn group across 1 directory with 6 updates #4

dependabot · 2025-09-11T00:48:14Z

Bumps the npm_and_yarn group with 6 updates in the / directory:

Package	From	To
vite	`5.4.19`	`5.4.20`
brace-expansion	`1.1.11`	`1.1.12`
esbuild	`0.21.5`	`0.25.9`
vitest	`1.6.1`	`3.2.4`
@vitejs/plugin-react-swc	`3.6.0`	`3.11.0`
vite	`5.4.20`	`7.1.5`
vite-plugin-pwa	`0.18.1`	`1.0.3`

Updates vite from 5.4.19 to 5.4.20

Release notes

Sourced from vite's releases.

v5.4.20

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

5.4.20 (2025-09-08)

fix: apply fs.strict check to HTML files (#20736) (482000f), closes #20736

Commits

997700f release: v5.4.20
482000f fix: apply fs.strict check to HTML files (#20736)
See full diff in compare view

Updates brace-expansion from 1.1.11 to 1.1.12

Release notes

Sourced from brace-expansion's releases.

v1.1.12

pkg: publish on tag 1.x c460dbd

fmt ccb8ac6

Fix potential ReDoS Vulnerability or Inefficient Regular Expression (#65) c3c73c8

juliangruber/brace-expansion@v1.1.11...v1.1.12

Commits

44f33b4 1.1.12
c460dbd pkg: publish on tag 1.x
ccb8ac6 fmt
c3c73c8 Fix potential ReDoS Vulnerability or Inefficient Regular Expression (#65)
See full diff in compare view

Updates esbuild from 0.21.5 to 0.25.9

Release notes

Sourced from esbuild's releases.

v0.25.9
Better support building projects that use Yarn on Windows (#3131, #3663)

With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the C: drive. The problem was as follows:

Yarn in Plug'n'Play mode on Windows stores its global module cache on the C: drive

Some developers put their projects on the D: drive

Yarn generates relative paths that use ../.. to get from the project directory to the cache directory

Windows-style paths don't support directory traversal between drives via .. (so D:\.. is just D:)

I didn't have access to a Windows machine for testing this edge case

Yarn works around this edge case by pretending Windows-style paths beginning with C:\ are actually Unix-style paths beginning with /C:/, so the ../.. path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.
Preserve parentheses around function expressions (#4252)

The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.

Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:
// Original code
const fn0 = () => 0
const fn1 = (() => 1)
console.log(fn0, function() { return fn1() }())
// Old output
const fn0 = () => 0;
const fn1 = () => 1;
console.log(fn0, function() {
return fn1();
}());
// New output
const fn0 = () => 0;
const fn1 = (() => 1);
console.log(fn0, (function() {
return fn1();
})());
Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.
Update Go from 1.23.10 to 1.23.12 (#4257, #4258)

This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.
v0.25.8

Fix another TypeScript parsing edge case (#4248)

This fixes a regression with a change in the previous release that tries to more accurately parse TypeScript arrow functions inside the ?: operator. The regression specifically involves parsing an arrow function containing a #private identifier inside the middle of a ?: ternary operator inside a class body. This was fixed by propagating private identifier state into the parser clone used to speculatively parse the arrow function body. Here is an example of some affected code:

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2024

This changelog documents all esbuild versions published in the year 2024 (versions 0.19.12 through 0.24.2).

0.24.2

Fix regression with --define and import.meta (#4010, #4012, #4013)

The previous change in version 0.24.1 to use a more expression-like parser for define values to allow quoted property names introduced a regression that removed the ability to use --define:import.meta=.... Even though import is normally a keyword that can't be used as an identifier, ES modules special-case the import.meta expression to behave like an identifier anyway. This change fixes the regression.

This fix was contributed by @sapphi-red.

0.24.1
Allow es2024 as a target in tsconfig.json (#4004)

TypeScript recently added es2024 as a compilation target, so esbuild now supports this in the target field of tsconfig.json files, such as in the following configuration file:
{
  "compilerOptions": {
    "target": "ES2024"
  }
}
As a reminder, the only thing that esbuild uses this field for is determining whether or not to use legacy TypeScript behavior for class fields. You can read more in the documentation.

This fix was contributed by @billyjanitsch.
Allow automatic semicolon insertion after get/set

This change fixes a grammar bug in the parser that incorrectly treated the following code as a syntax error:
class Foo {
  get
  *x() {}
  set
  *y() {}
}
The above code will be considered valid starting with this release. This change to esbuild follows a similar change to TypeScript which will allow this syntax starting with TypeScript 5.7.
Allow quoted property names in --define and --pure (#4008)

The define and pure API options now accept identifier expressions containing quoted property names. Previously all identifiers in the identifier expression had to be bare identifiers. This change now makes --define and --pure consistent with --global-name, which already supported quoted property names. For example, the following is now possible:

... (truncated)

Commits

195e05c publish 0.25.9 to npm
3dac33f fix #3131, fix #3663: yarnpnp + windows + D drive
0f2c5c8 mock fs now supports multiple volumes on windows
100a51e split out yarnpnp snapshot tests
13aace3 remove C: assumption from windows snapshot tests
f1f413f fix #4252: preserve parentheses around functions
1bc8091 fix #4257, close #4258: go 1.23.10 => 1.23.12
bc52135 move the go compiler version to go.version
a0af5d1 makefile: use ESBUILD_VERSION consistently
8c71947 publish 0.25.8 to npm
Additional commits viewable in compare view

Updates vitest from 1.6.1 to 3.2.4

Release notes

Sourced from vitest's releases.

v3.2.4

   🐞 Bug Fixes

Use correct path for optimisation of strip-literal - by @mrginglymus in vitest-dev/vitest#8139 (44940)

Print uint and buffer as a simple string - by @sheremet-va in vitest-dev/vitest#8141 (b86bf)

browser:

Show a helpful error when spying on an export - by @sheremet-va in vitest-dev/vitest#8178 (56007)

cli:

vitest run --watch should be watch-mode - by @AriPerkkio in vitest-dev/vitest#8128 (657e8)

Use absolute path environment on Windows - by @colinaaa in vitest-dev/vitest#8105 (85dc0)

Throw error when --shard x/<count> exceeds count of test files - by @AriPerkkio in vitest-dev/vitest#8112 (8a18c)

coverage:

Ignore SCSS in browser mode - by @sheremet-va in vitest-dev/vitest#8161 (0c3be)

deps:

Update all non-major dependencies - in vitest-dev/vitest#8123 (93f32)

expect:

Handle async errors in expect.soft - by @lzl0304 in vitest-dev/vitest#8145 (68699)

pool:

Auto-adjust minWorkers when only maxWorkers specified - by @AriPerkkio in vitest-dev/vitest#8110 (14dc0)

reporter:

task.meta should be available in custom reporter's errors - by @AriPerkkio in vitest-dev/vitest#8115 (27df6)

runner:

Preserve handler wrapping on extend - by @pengooseDev in vitest-dev/vitest#8153 (a9281)

ui:

Ensure ui config option works correctly - by @lzl0304 in vitest-dev/vitest#8147 (42eeb)

    View changes on GitHub

v3.2.3

   🚀 Features

browser: Use base url instead of vitest - by @sheremet-va in vitest-dev/vitest#8126 (1d8eb)

ui: Show test annotations and metadata in the test report tab - by @sheremet-va in vitest-dev/vitest#8093 (c69be)

   🐞 Bug Fixes

Rerun tests when project's setup file is changed - by @sheremet-va in vitest-dev/vitest#8097 (0f335)

Revert expect.any return type - by @sheremet-va in vitest-dev/vitest#8129 (47514)

Run only the name plugin last, not all config plugins - by @sheremet-va in vitest-dev/vitest#8130 (83862)

pool:

Throw if user's tests use process.send() - by @AriPerkkio in vitest-dev/vitest#8125 (dfe81)

runner:

Fast sequential task updates missing - by @AriPerkkio in vitest-dev/vitest#8121 (7bd11)

Comments between fixture destructures - by @AriPerkkio in vitest-dev/vitest#8127 (dc469)

vite-node:

Unable to handle errors where sourcemap mapping empty - by @blake-newman and @hi-ogawa in vitest-dev/vitest#8071 (8aa25)

    View changes on GitHub

v3.2.2

... (truncated)

Commits

c666d14 chore: release v3.2.4
8a18c8e fix(cli): throw error when --shard x/\<count> exceeds count of test files (#...
8abd7cc chore(deps): update tinypool (#8174)
93f3200 fix(deps): update all non-major dependencies (#8123)
0c3be6f fix(coverage): ignore SCSS in browser mode (#8161)
790bc31 chore: update deprecation notice for globs (#8148)
c0eae7d chore: update deprecated workspace file log (#8118)
14dc072 fix(pool): auto-adjust minWorkers when only maxWorkers specified (#8110)
85dc019 fix(cli): use absolute path environment on Windows (#8105)
27df68a fix(reporter): task.meta should be available in custom reporter's errors (#...
Additional commits viewable in compare view

Updates @vitejs/plugin-react-swc from 3.6.0 to 3.11.0

Release notes

Sourced from @vitejs/plugin-react-swc's releases.

[email protected]

Add HMR support for compound components (#518)

HMR now works for compound components like this:
const Root = () => <div>Accordion Root</div>
const Item = () => <div>Accordion Item</div>
export const Accordion = { Root, Item }
Return Plugin[] instead of PluginOption[] (#537)

The return type has changed from react(): PluginOption[] to more specialized type react(): Plugin[]. This allows for type-safe manipulation of plugins, for example:
// previously this causes type errors
react()
  .map(p => ({ ...p, applyToEnvironment: e => e.name === 'client' }))
[email protected]

Suggest @vitejs/plugin-react-oxc if rolldown-vite is detected #491

Emit a log which recommends @vitejs/plugin-react-oxc when rolldown-vite is detected to improve performance and use Oxc under the hood. The warning can be disabled by setting disableOxcRecommendation: false in the plugin options.

Use optimizeDeps.rollupOptions instead of optimizeDeps.esbuildOptions for rolldown-vite #489

This suppresses the warning about optimizeDeps.esbuildOptions being deprecated in rolldown-vite.

Add Vite 7-beta to peerDependencies range #497

React plugins are compatible with Vite 7, this removes the warning when testing the beta.

[email protected]

Add explicit semicolon in preambleCode #485

This fixes an edge case when using HTML minifiers that strips line breaks aggressively.

[email protected]

Add filter for rolldown-vite #470

Added filter so that it is more performant when running this plugin with rolldown-powered version of Vite.

Skip HMR preamble in Vitest browser mode #478

This was causing annoying Sourcemap for "/@react-refresh" points to missing source files and is unnecessary in test mode.

Skip HMR for JSX files with hooks #480

... (truncated)

Changelog

Sourced from @vitejs/plugin-react-swc's changelog.

3.11.0 (2025-07-18)

Add HMR support for compound components (#518)

HMR now works for compound components like this:
const Root = () => <div>Accordion Root</div>
const Item = () => <div>Accordion Item</div>
export const Accordion = { Root, Item }
Return Plugin[] instead of PluginOption[] (#537)

The return type has changed from react(): PluginOption[] to more specialized type react(): Plugin[]. This allows for type-safe manipulation of plugins, for example:
// previously this causes type errors
react()
  .map(p => ({ ...p, applyToEnvironment: e => e.name === 'client' }))
3.10.2 (2025-06-10)

Suggest @vitejs/plugin-react-oxc if rolldown-vite is detected #491

Emit a log which recommends @vitejs/plugin-react-oxc when rolldown-vite is detected to improve performance and use Oxc under the hood. The warning can be disabled by setting disableOxcRecommendation: true in the plugin options.

Use optimizeDeps.rollupOptions instead of optimizeDeps.esbuildOptions for rolldown-vite #489

This suppresses the warning about optimizeDeps.esbuildOptions being deprecated in rolldown-vite.

Add Vite 7-beta to peerDependencies range #497

React plugins are compatible with Vite 7, this removes the warning when testing the beta.

3.10.1 (2025-06-03)

Add explicit semicolon in preambleCode #485

This fixes an edge case when using HTML minifiers that strips line breaks aggressively.

3.10.0 (2025-05-23)

Add filter for rolldown-vite #470

Added filter so that it is more performant when running this plugin with rolldown-powered version of Vite.

Skip HMR preamble in Vitest browser mode #478

... (truncated)

Commits

See full diff in compare view

Updates vite from 5.4.20 to 7.1.5

Release notes

Sourced from vite's releases.

v5.4.20

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

5.4.20 (2025-09-08)

fix: apply fs.strict check to HTML files (#20736) (482000f), closes #20736

Commits

997700f release: v5.4.20
482000f fix: apply fs.strict check to HTML files (#20736)
See full diff in compare view

Updates vite-plugin-pwa from 0.18.1 to 1.0.3

Release notes

Sourced from vite-plugin-pwa's releases.

v1.0.3

   🐞 Bug Fixes

Add origin to scope_extensions to comply with the spec and get rid of warning - by @CodingDive in vite-pwa/vite-plugin-pwa#880 (aa078)

   🏎 Performance

Add hook filters - by @sapphi-red in vite-pwa/vite-plugin-pwa#877 (db4ec)

    View changes on GitHub

v1.0.2

   🚀 Features

pwa-assets: Add additional checks to resolve images - by @userquin in vite-pwa/vite-plugin-pwa#876 (03404)

    View changes on GitHub

v1.0.1

   🐞 Bug Fixes

Added vite 7.0.0 support - by @hasanparasteh in vite-pwa/vite-plugin-pwa#868 (34229)

    View changes on GitHub

v1.0.0

   🚨 Breaking Changes

Update @vite-pwa/assets-generator to v1.0.0 - by @userquin in vite-pwa/vite-plugin-pwa#846 (1c570)

   🐞 Bug Fixes

Avoid assigning to bundle object - by @sapphi-red in vite-pwa/vite-plugin-pwa#843 (b0716)

    View changes on GitHub

v0.21.2

   🐞 Bug Fixes

manifest: Default manifest theme_color and description not being applied - by @alexandre-hallaine in vite-pwa/vite-plugin-pwa#839 (53568)

    View changes on GitHub

v0.21.1

   🚀 Features

Support Vite 6 - by @gabrielrbarbosa and @userquin in vite-pwa/vite-plugin-pwa#797 (c4c25)

html: Add head when missing from entry point - by @userquin in vite-pwa/vite-plugin-pwa#784 (856d3)

   🐞 Bug Fixes

... (truncated)

Commits

84e66d7 chore: release v1.0.3
aa07862 fix: add origin to scope_extensions to comply with the spec and get rid of wa...
8247192 docs: proper default (#848)
db4ecdb perf: add hook filters (#877)
4385f0a chore: release v1.0.2
9b650a1 chore: update pnpm to v10.13.1
0340498 feat(pwa-assets): add additional checks to resolve images (#876)
9fd1a03 chore: release v1.0.1
1967829 chore: update pnpm to v10.12.4 (#870)
3422925 fix: added vite 7.0.0 support (#868)
Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

@dependabot rebase will rebase this PR
@dependabot recreate will recreate this PR, overwriting any edits that have been made to it
@dependabot merge will merge this PR after your CI passes on it
@dependabot squash and merge will squash and merge this PR after your CI passes on it
@dependabot cancel merge will cancel a previously requested merge and block automerging
@dependabot reopen will reopen this PR if it is closed
@dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
@dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
@dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps the npm_and_yarn group with 6 updates in the / directory: | Package | From | To | | --- | --- | --- | | [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `5.4.19` | `5.4.20` | | [brace-expansion](https://github.com/juliangruber/brace-expansion) | `1.1.11` | `1.1.12` | | [esbuild](https://github.com/evanw/esbuild) | `0.21.5` | `0.25.9` | | [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `1.6.1` | `3.2.4` | | [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react/tree/HEAD/packages/plugin-react-swc) | `3.6.0` | `3.11.0` | | [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) | `5.4.20` | `7.1.5` | | [vite-plugin-pwa](https://github.com/vite-pwa/vite-plugin-pwa) | `0.18.1` | `1.0.3` | Updates `vite` from 5.4.19 to 5.4.20 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v5.4.20/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v5.4.20/packages/vite) Updates `brace-expansion` from 1.1.11 to 1.1.12 - [Release notes](https://github.com/juliangruber/brace-expansion/releases) - [Commits](juliangruber/brace-expansion@1.1.11...v1.1.12) Updates `esbuild` from 0.21.5 to 0.25.9 - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2024.md) - [Commits](evanw/esbuild@v0.21.5...v0.25.9) Updates `vitest` from 1.6.1 to 3.2.4 - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v3.2.4/packages/vitest) Updates `@vitejs/plugin-react-swc` from 3.6.0 to 3.11.0 - [Release notes](https://github.com/vitejs/vite-plugin-react/releases) - [Changelog](https://github.com/vitejs/vite-plugin-react/blob/main/packages/plugin-react-swc/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite-plugin-react/commits/[email protected]/packages/plugin-react-swc) Updates `vite` from 5.4.20 to 7.1.5 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v5.4.20/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v5.4.20/packages/vite) Updates `vite-plugin-pwa` from 0.18.1 to 1.0.3 - [Release notes](https://github.com/vite-pwa/vite-plugin-pwa/releases) - [Commits](vite-pwa/vite-plugin-pwa@v0.18.1...v1.0.3) --- updated-dependencies: - dependency-name: vite dependency-version: 5.4.20 dependency-type: direct:development dependency-group: npm_and_yarn - dependency-name: brace-expansion dependency-version: 1.1.12 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: esbuild dependency-version: 0.25.9 dependency-type: indirect dependency-group: npm_and_yarn - dependency-name: vitest dependency-version: 3.2.4 dependency-type: direct:development dependency-group: npm_and_yarn - dependency-name: "@vitejs/plugin-react-swc" dependency-version: 3.11.0 dependency-type: direct:development dependency-group: npm_and_yarn - dependency-name: vite dependency-version: 7.1.5 dependency-type: direct:development dependency-group: npm_and_yarn - dependency-name: vite-plugin-pwa dependency-version: 1.0.3 dependency-type: direct:development dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <[email protected]>

dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 11, 2025

DougReeder force-pushed the main branch from 50e1d11 to e4444ed Compare September 11, 2025 02:00

dependabot bot force-pushed the dependabot/npm_and_yarn/npm_and_yarn-e9103c20be branch from fde5c63 to b3d4208 Compare September 14, 2025 19:56

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Bump the npm_and_yarn group across 1 directory with 6 updates #4

Bump the npm_and_yarn group across 1 directory with 6 updates #4

Uh oh!

dependabot bot commented on behalf of github Sep 11, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Bump the npm_and_yarn group across 1 directory with 6 updates #4

Are you sure you want to change the base?

Bump the npm_and_yarn group across 1 directory with 6 updates #4

Uh oh!

Conversation

dependabot bot commented on behalf of github Sep 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

v5.4.20

5.4.20 (2025-09-08)

v1.1.12

v0.25.9

v0.25.8

Changelog: 2024

0.24.2

0.24.1

v3.2.4

🐞 Bug Fixes

v3.2.3

🚀 Features

🐞 Bug Fixes

v3.2.2

Add HMR support for compound components (#518)

Return Plugin[] instead of PluginOption[] (#537)

Suggest @vitejs/plugin-react-oxc if rolldown-vite is detected #491

Use optimizeDeps.rollupOptions instead of optimizeDeps.esbuildOptions for rolldown-vite #489

Add Vite 7-beta to peerDependencies range #497

Add explicit semicolon in preambleCode #485

Add filter for rolldown-vite #470

Skip HMR preamble in Vitest browser mode #478

Skip HMR for JSX files with hooks #480

3.11.0 (2025-07-18)

Add HMR support for compound components (#518)

Return Plugin[] instead of PluginOption[] (#537)

3.10.2 (2025-06-10)

Suggest @vitejs/plugin-react-oxc if rolldown-vite is detected #491

Use optimizeDeps.rollupOptions instead of optimizeDeps.esbuildOptions for rolldown-vite #489

Add Vite 7-beta to peerDependencies range #497

3.10.1 (2025-06-03)

Add explicit semicolon in preambleCode #485

3.10.0 (2025-05-23)

Add filter for rolldown-vite #470

Skip HMR preamble in Vitest browser mode #478

v5.4.20

5.4.20 (2025-09-08)

v1.0.3

🐞 Bug Fixes

🏎 Performance

v1.0.2

🚀 Features

v1.0.1

🐞 Bug Fixes

v1.0.0

🚨 Breaking Changes

🐞 Bug Fixes

v0.21.2

🐞 Bug Fixes

v0.21.1

🚀 Features

🐞 Bug Fixes

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

dependabot bot commented on behalf of github Sep 11, 2025 •

edited

Loading

Return `Plugin[]` instead of `PluginOption[]` (#537)

Suggest `@vitejs/plugin-react-oxc` if rolldown-vite is detected #491

Use `optimizeDeps.rollupOptions` instead of `optimizeDeps.esbuildOptions` for rolldown-vite #489

Add `filter` for rolldown-vite #470

Return `Plugin[]` instead of `PluginOption[]` (#537)

Suggest `@vitejs/plugin-react-oxc` if rolldown-vite is detected #491

Use `optimizeDeps.rollupOptions` instead of `optimizeDeps.esbuildOptions` for rolldown-vite #489

Add `filter` for rolldown-vite #470