Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 21, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@playwright/test (source) ^1.51.1 -> ^1.52.0 age adoption passing confidence
@shikijs/transformers (source) ^3.2.2 -> ^3.3.0 age adoption passing confidence
@shikijs/vitepress-twoslash (source) ^3.2.2 -> ^3.3.0 age adoption passing confidence
@vitejs/plugin-react (source) ^4.3.4 -> ^4.4.1 age adoption passing confidence
@wdio/types (source) ^9.12.3 -> ^9.12.6 age adoption passing confidence
es-module-lexer ^1.6.0 -> ^1.7.0 age adoption passing confidence
esbuild ^0.25.2 -> ^0.25.3 age adoption passing confidence
msw (source) ^2.7.4 -> ^2.7.5 age adoption passing confidence
playwright (source) ^1.51.1 -> ^1.52.0 age adoption passing confidence
playwright-core (source) ^1.51.1 -> ^1.52.0 age adoption passing confidence
pnpm (source) 10.8.1 -> 10.9.0 age adoption passing confidence
sweetalert2 (source) ^11.18.0 -> ^11.19.1 age adoption passing confidence
unplugin-isolated-decl ^0.13.6 -> ^0.13.9 age adoption passing confidence
unplugin-oxc ^0.3.3 -> ^0.3.5 age adoption passing confidence
unplugin-swc (source) ^1.5.1 -> ^1.5.2 age adoption passing confidence
vitepress (source) 2.0.0-alpha.4 -> 2.0.0-alpha.5 age adoption passing confidence
webdriverio (source) ^9.12.5 -> ^9.12.7 age adoption passing confidence
zx (source) ^8.5.2 -> ^8.5.3 age adoption passing confidence

Release Notes

microsoft/playwright (@​playwright/test)

v1.52.0

Compare Source

shikijs/shiki (@​shikijs/transformers)

v3.3.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
vitejs/vite-plugin-react (@​vitejs/plugin-react)

v4.4.1

Compare Source

Fix type issue when using moduleResolution: "node" in tsconfig #​462

v4.4.0

Compare Source

Make compatible with rolldown-vite

This plugin is now compatible with rolldown-powered version of Vite.
Note that currently the __source property value position might be incorrect. This will be fixed in the near future.

webdriverio/webdriverio (@​wdio/types)

v9.12.6

Compare Source

🚀 New Feature
  • webdriver
🐛 Bug Fix
💅 Polish
Committers: 4
guybedford/es-module-lexer (es-module-lexer)

v1.7.0

Compare Source

What's Changed

Full Changelog: guybedford/es-module-lexer@1.6.0...1.7.0

evanw/esbuild (esbuild)

v0.25.3

Compare Source

  • Fix lowered async arrow functions before super() (#​4141, #​4142)

    This change makes it possible to call an async arrow function in a constructor before calling super() when targeting environments without async support, as long as the function body doesn't reference this. Here's an example (notice the change from this to null):

    // Original code
    class Foo extends Object {
      constructor() {
        (async () => await foo())()
        super()
      }
    }
    
    // Old output (with --target=es2016)
    class Foo extends Object {
      constructor() {
        (() => __async(this, null, function* () {
          return yield foo();
        }))();
        super();
      }
    }
    
    // New output (with --target=es2016)
    class Foo extends Object {
      constructor() {
        (() => __async(null, null, function* () {
          return yield foo();
        }))();
        super();
      }
    }

    Some background: Arrow functions with the async keyword are transformed into generator functions for older language targets such as --target=es2016. Since arrow functions capture this, the generated code forwards this into the body of the generator function. However, JavaScript class syntax forbids using this in a constructor before calling super(), and this forwarding was problematic since previously happened even when the function body doesn't use this. Starting with this release, esbuild will now only forward this if it's used within the function body.

    This fix was contributed by @​magic-akari.

  • Fix memory leak with --watch=true (#​4131, #​4132)

    This release fixes a memory leak with esbuild when --watch=true is used instead of --watch. Previously using --watch=true caused esbuild to continue to use more and more memory for every rebuild, but --watch=true should now behave like --watch and not leak memory.

    This bug happened because esbuild disables the garbage collector when it's not run as a long-lived process for extra speed, but esbuild's checks for which arguments cause esbuild to be a long-lived process weren't updated for the new --watch=true style of boolean command-line flags. This has been an issue since this boolean flag syntax was added in version 0.14.24 in 2022. These checks are unfortunately separate from the regular argument parser because of how esbuild's internals are organized (the command-line interface is exposed as a separate Go API so you can build your own custom esbuild CLI).

    This fix was contributed by @​mxschmitt.

  • More concise output for repeated legal comments (#​4139)

    Some libraries have many files and also use the same legal comment text in all files. Previously esbuild would copy each legal comment to the output file. Starting with this release, legal comments duplicated across separate files will now be grouped in the output file by unique comment content.

  • Allow a custom host with the development server (#​4110)

    With this release, you can now use a custom non-IP host with esbuild's local development server (either with --serve= for the CLI or with the serve() call for the API). This was previously possible, but was intentionally broken in version 0.25.0 to fix a security issue. This change adds the functionality back except that it's now opt-in and only for a single domain name that you provide.

    For example, if you add a mapping in your /etc/hosts file from local.example.com to 127.0.0.1 and then use esbuild --serve=local.example.com:8000, you will now be able to visit http://local.example.com:8000/ in your browser and successfully connect to esbuild's development server (doing that would previously have been blocked by the browser). This should also work with HTTPS if it's enabled (see esbuild's documentation for how to do that).

  • Add a limit to CSS nesting expansion (#​4114)

    With this release, esbuild will now fail with an error if there is too much CSS nesting expansion. This can happen when nested CSS is converted to CSS without nesting for older browsers as expanding CSS nesting is inherently exponential due to the resulting combinatorial explosion. The expansion limit is currently hard-coded and cannot be changed, but is extremely unlikely to trigger for real code. It exists to prevent esbuild from using too much time and/or memory. Here's an example:

    a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}

    Previously, transforming this file with --target=safari1 took 5 seconds and generated 40mb of CSS. Trying to do that will now generate the following error instead:

    ✘ [ERROR] CSS nesting is causing too much expansion
    
        example.css:1:60:
          1 │ a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{a,b{color:red}}}}}}}}}}}}}}}}}}}}
            ╵                                                             ^
    
      CSS nesting expansion was terminated because a rule was generated with 65536 selectors. This limit
      exists to prevent esbuild from using too much time and/or memory. Please change your CSS to use
      fewer levels of nesting.
    
  • Fix path resolution edge case (#​4144)

    This fixes an edge case where esbuild's path resolution algorithm could deviate from node's path resolution algorithm. It involves a confusing situation where a directory shares the same file name as a file (but without the file extension). See the linked issue for specific details. This appears to be a case where esbuild is correctly following node's published resolution algorithm but where node itself is doing something different. Specifically the step LOAD_AS_FILE appears to be skipped when the input ends with ... This release changes esbuild's behavior for this edge case to match node's behavior.

  • Update Go from 1.23.7 to 1.23.8 (#​4133, #​4134)

    This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain reports from vulnerability scanners that detect which version of the Go compiler esbuild uses, such as for CVE-2025-22871.

    As a reminder, esbuild's development server is intended for development, not for production, so I do not consider most networking-related vulnerabilities in Go to be vulnerabilities in esbuild. Please do not use esbuild's development server in production.

mswjs/msw (msw)

v2.7.5

Compare Source

v2.7.5 (2025-04-18)

Bug Fixes
pnpm/pnpm (pnpm)

v10.9.0

Compare Source

Minor Changes
  • Added support for installing JSR packages. You can now install JSR packages using the following syntax:

    pnpm add jsr:<pkg_name>
    

    or with a version range:

    pnpm add jsr:<pkg_name>@&#8203;<range>
    

    For example, running:

    pnpm add jsr:@&#8203;foo/bar
    

    will add the following entry to your package.json:

    {
      "dependencies": {
        "@&#8203;foo/bar": "jsr:^0.1.2"
      }
    }

    When publishing, this entry will be transformed into a format compatible with npm, older versions of Yarn, and previous pnpm versions:

    {
      "dependencies": {
        "@&#8203;foo/bar": "npm:@&#8203;jsr/foo__bar@^0.1.2"
      }
    }

    Related issue: #​8941.

    Note: The @jsr scope defaults to https://npm.jsr.io/ if the @jsr:registry setting is not defined.

  • Added a new setting, dangerouslyAllowAllBuilds, for automatically running any scripts of dependencies without the need to approve any builds. It was already possible to allow all builds by adding this to pnpm-workspace.yaml:

    neverBuiltDependencies: []

    dangerouslyAllowAllBuilds has the same effect but also allows to be set globally via:

    pnpm config set dangerouslyAllowAllBuilds true
    

    It can also be set when running a command:

    pnpm install --dangerously-allow-all-builds
    
Patch Changes
  • Fix a false negative in verifyDepsBeforeRun when nodeLinker is hoisted and there is a workspace package without dependencies and node_modules directory #​9424.
  • Explicitly drop verifyDepsBeforeRun support for nodeLinker: pnp. Combining verifyDepsBeforeRun and nodeLinker: pnp will now print a warning.
sweetalert2/sweetalert2 (sweetalert2)

v11.19.1

Compare Source

Bug Fixes

v11.19.0

Compare Source

Features
unplugin/unplugin-isolated-decl (unplugin-isolated-decl)

v0.13.9

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.13.8

Compare Source

No significant changes

    View changes on GitHub

v0.13.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
unplugin/unplugin-oxc (unplugin-oxc)

v0.3.5

Compare Source

   🚀 Features
    View changes on GitHub

v0.3.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
unplugin/unplugin-swc (unplugin-swc)

v1.5.2

Compare Source

vuejs/vitepress (vitepress)

v2.0.0-alpha.5

Compare Source

Bug Fixes
Features
Performance Improvements
  • call module.enableCompileCache() (70de34c)
  • hoist expensive operations in useLayout (e5ab067)
BREAKING CHANGES
  • useLocalNav and useSidebar are removed in favor of useLayout. To migrate, just do find and replace. Sidebar controls are no longer exported, but we didn't find any usage on GitHub. If there is demand, we can export respective composables later. DefaultTheme.DocSidebar and DefaultTheme.DocLocalNav types are also removed.
  • vp-adaptive-theme class is no longer added to code blocks when there is single theme. Theme authors supporting single code theme can use .shiki:not(.shiki-themes) as selector. Alternatively, it might be better to use the bg/fg variables set on the .shiki block to keep things generic.
  • vp-code class is no longer added to code blocks. Use .shiki or pre.shiki or [class*='language-'] pre instead. People not customizing their themes are not affected.
google/zx (zx)

v8.5.3: — Trap Master

Compare Source

  • Another portion of JSR related improvements #​1193 #​1192
  • Goods refactoring #​1195
    • Fixes expBackoff implementation
    • Sets $.log.output as default spinner() output
    • Makes configurable question() I/O
  • Added Graaljs compatability test #​1194
  • Docs improvements, usage examples updates #​1198

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.


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

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

@hi-ogawa
Copy link
Contributor

hi-ogawa commented Apr 21, 2025

Build error is due to unplugin/unplugin-isolated-decl#67. Maybe it's time to try tsdown which should eliminate the need of many plugins. https://github.com/rolldown/tsdown

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from caca03e to 0b37384 Compare April 22, 2025 22:46
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Apr 22, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0b37384 to b3c6d1e Compare April 23, 2025 05:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from b3c6d1e to 99189f7 Compare April 23, 2025 13:43
@netlify
Copy link

netlify bot commented Apr 23, 2025

Deploy Preview for vitest-dev ready!

Name Link
🔨 Latest commit 99189f7
🔍 Latest deploy log https://app.netlify.com/sites/vitest-dev/deploys/6808ee924b521b0008715b6e
😎 Deploy Preview https://deploy-preview-7867--vitest-dev.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants