Skip to content

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Apr 7, 2025

Bumps esbuild to 0.25.2 and updates ancestor dependencies esbuild, vitest, @vitejs/plugin-react-swc, orval and vite. These dependencies need to be updated together.

Updates esbuild from 0.19.8 to 0.25.2

Release notes

Sourced from esbuild's releases.

v0.25.2

  • Support flags in regular expressions for the API (#4121)

    The JavaScript plugin API for esbuild takes JavaScript regular expression objects for the filter option. Internally these are translated into Go regular expressions. However, this translation previously ignored the flags property of the regular expression. With this release, esbuild will now translate JavaScript regular expression flags into Go regular expression flags. Specifically the JavaScript regular expression /\.[jt]sx?$/i is turned into the Go regular expression `(?i)\.[jt]sx?$` internally inside of esbuild's API. This should make it possible to use JavaScript regular expressions with the i flag. Note that JavaScript and Go don't support all of the same regular expression features, so this mapping is only approximate.

  • Fix node-specific annotations for string literal export names (#4100)

    When node instantiates a CommonJS module, it scans the AST to look for names to expose via ESM named exports. This is a heuristic that looks for certain patterns such as exports.NAME = ... or module.exports = { ... }. This behavior is used by esbuild to "annotate" CommonJS code that was converted from ESM with the original ESM export names. For example, when converting the file export let foo, bar from ESM to CommonJS, esbuild appends this to the end of the file:

    // Annotate the CommonJS export names for ESM import in node:
    0 && (module.exports = {
      bar,
      foo
    });

    However, this feature previously didn't work correctly for export names that are not valid identifiers, which can be constructed using string literal export names. The generated code contained a syntax error. That problem is fixed in this release:

    // Original code
    let foo
    export { foo as "foo!" }
    // Old output (with --format=cjs --platform=node)
    ...
    0 && (module.exports = {
    "foo!"
    });
    // New output (with --format=cjs --platform=node)
    ...
    0 && (module.exports = {
    "foo!": null
    });

  • Basic support for index source maps (#3439, #4109)

    The source map specification has an optional mode called index source maps that makes it easier for tools to create an aggregate JavaScript file by concatenating many smaller JavaScript files with source maps, and then generate an aggregate source map by simply providing the original source maps along with some offset information. My understanding is that this is rarely used in practice. I'm only aware of two uses of it in the wild: ClojureScript and Turbopack.

    This release provides basic support for indexed source maps. However, the implementation has not been tested on a real app (just on very simple test input). If you are using index source maps in a real app, please try this out and report back if anything isn't working for you.

    Note that this is also not a complete implementation. For example, index source maps technically allows nesting source maps to an arbitrary depth, while esbuild's implementation in this release only supports a single level of nesting. It's unclear whether supporting more than one level of nesting is important or not given the lack of available test cases.

    This feature was contributed by @​clyfish.

v0.25.1

... (truncated)

Changelog

Sourced from esbuild's changelog.

Changelog: 2023

This changelog documents all esbuild versions published in the year 2023 (versions 0.16.13 through 0.19.11).

0.19.11

  • Fix TypeScript-specific class transform edge case (#3559)

    The previous release introduced an optimization that avoided transforming super() in the class constructor for TypeScript code compiled with useDefineForClassFields set to false if all class instance fields have no initializers. The rationale was that in this case, all class instance fields are omitted in the output so no changes to the constructor are needed. However, if all of this is the case and there are #private instance fields with initializers, those private instance field initializers were still being moved into the constructor. This was problematic because they were being inserted before the call to super() (since super() is now no longer transformed in that case). This release introduces an additional optimization that avoids moving the private instance field initializers into the constructor in this edge case, which generates smaller code, matches the TypeScript compiler's output more closely, and avoids this bug:

    // Original code
    class Foo extends Bar {
      #private = 1;
      public: any;
      constructor() {
        super();
      }
    }
    // Old output (with esbuild v0.19.9)
    class Foo extends Bar {
    constructor() {
    super();
    this.#private = 1;
    }
    #private;
    }
    // Old output (with esbuild v0.19.10)
    class Foo extends Bar {
    constructor() {
    this.#private = 1;
    super();
    }
    #private;
    }
    // New output
    class Foo extends Bar {
    #private = 1;
    constructor() {
    super();
    }
    }

  • Minifier: allow reording a primitive past a side-effect (#3568)

    The minifier previously allowed reordering a side-effect past a primitive, but didn't handle the case of reordering a primitive past a side-effect. This additional case is now handled:

... (truncated)

Commits

Updates vitest from 0.34.6 to 3.1.1

Release notes

Sourced from vitest's releases.

v3.1.1

   🐞 Bug Fixes

    View changes on GitHub

v3.1.0

🚀 Features

🐞 Bug Fixes

🏎 Performance

... (truncated)

Commits
  • a9d36c7 chore: release v3.1.1
  • 69ca425 fix(reporter): print test only once in the verbose mode (#7738)
  • b166efa fix(reporter): report tests in correct order (#7752)
  • b8eda4b chore: release v3.1.0
  • 938da77 fix (ui): rerun individually tests with special chars in name (#7707)
  • 7883acd feat: use providers request interception for module mocking (#7576)
  • a7ecd0f refactor: remove direct imports from rollup (#7751)
  • 5659a0e feat: Added vitest-browser-lit to vitest init browser and docs (#7705)
  • 2702cf4 fix: fix vm tests flakiness (#7741)
  • 12762ea perf(browser): fork jest-dom instead of bundling it (#7605)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by vitestbot, a new releaser for vitest since your current version.


Updates @vitejs/plugin-react-swc from 3.5.0 to 3.8.1

Release notes

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

v3.8.1

Remove WebContainers warning #268

SWC is now supported in WebContainers 🎉

v3.8.0

Add useAtYourOwnRisk_mutateSwcOptions option

The future of Vite is with OXC, and from the beginning this was a design choice to not exposed too many specialties from SWC so that Vite React users can move to another transformer later. Also debugging why some specific version of decorators with some other unstable/legacy feature doesn't work is not fun, so we won't provide support for it, hence the name useAtYourOwnRisk.

react({
  useAtYourOwnRisk_mutateSwcOptions(options) {
    options.jsc.parser.decorators = true;
    options.jsc.transform.decoratorVersion = "2022-03";
  },
});

v3.7.2

Add Vite 6 to peerDependencies range #207

Thanks @​RobinTail

Revert throw when refresh runtime is loaded twice #237

Revert the throw when refresh runtime is loaded twice to enable usage in micro frontend apps. This was added to help fix setup usage, and this is not worth an annoying warning for others or a config parameter.

This revert was done in the Babel plugin last year and I didn't port it back.

v3.7.1

Ignore directive sourcemap error #231

v3.7.0

Support HMR for class components

This is a long overdue and should fix some issues people had with HMR when migrating from CRA.

v3.6.0

Add parserConfig option

This will unlock to use the plugin in some use cases where the original source code is not in TS. Using this option to keep using JSX inside .js files is highly discouraged and can be removed in any future version.

Changelog

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

3.8.1

Remove WebContainers warning #268

SWC is now supported in WebContainers 🎉

3.8.0

Add useAtYourOwnRisk_mutateSwcOptions option

The future of Vite is with OXC, and from the beginning this was a design choice to not exposed too many specialties from SWC so that Vite React users can move to another transformer later. Also debugging why some specific version of decorators with some other unstable/legacy feature doesn't work is not fun, so we won't provide support for it, hence the name useAtYourOwnRisk.

react({
  useAtYourOwnRisk_mutateSwcOptions(options) {
    options.jsc.parser.decorators = true;
    options.jsc.transform.decoratorVersion = "2022-03";
  },
});

3.7.2

Add Vite 6 to peerDependencies range #207

Thanks @​RobinTail

Revert throw when refresh runtime is loaded twice #237

Revert the throw when refresh runtime is loaded twice to enable usage in micro frontend apps. This was added to help fix setup usage, and this is not worth an annoying warning for others or a config parameter.

This revert was done in the Babel plugin last year and I didn't port it back.

3.7.1

Ignore directive sourcemap error #231

3.7.0

Support HMR for class components

This is a long overdue and should fix some issues people had with HMR when migrating from CRA.

3.6.0

Add parserConfig option

This will unlock to use the plugin in some use cases where the original source code is not in TS. Using this option to keep using JSX inside .js files is highly discouraged and can be removed in any future version.

Commits

Updates orval from 6.22.1 to 7.8.0

Release notes

Sourced from orval's releases.

Release 7.8.0

7.8.0 (2025-04-03)

Bug Fixes

  • core: correctly import custom error and body types (#1977) (82675a4)
  • fetch: add default response if none provided (#1982) (d566fe4)
  • msw: nested ref fixes (#1983) (4be4caa)
  • reintroduce fix for native enums (#1957) (3221aae)
  • upgrade axios to ^1.8.2 and fix tsx errors (#1976) (33a37b3), closes #1971
  • zod: always prioritize required definitions to determine optional() (#1985) (752a540)
  • zod: correct tuple function mapping (#2006) (9185b97)
  • zod: enum schema generation for various types (#1996) (8cfb83e)
  • zod: handle $ref property names in schemas correctly (#1999) (1881dfa)

Features

  • add optional queryClient argument (#1992) (456037c)
  • core: add support for more enumname extensions (#2005) (994cc86)
  • query: add optional queryClient argument to mutations when using TanStack v5 (#1993) (e106067)
  • zod: add output.orverride.zod.datetimeOptions option (#1984) (b4eca05)

Release 7.7.0

7.7.0 (2025-03-13)

Bug Fixes

  • await asyncReduce in generateSpecs (#1950) (6dd8501)
  • display correct amount of duplicate schemas (#1958) (52d4c6f)
  • generate type for empty property (#1949) (8815e6b)
  • query: correctly check arg numbers, add operation info, add docs (#1974) (329218a)

Features

Release 7.6.0

7.6.0 (2025-02-27)

Bug Fixes

  • adjustments to native enums (#1882) (fcd942b)
  • core: don't union required with already required props (#1878) (3d122c3)
  • core: Fixed workspace setting does not append a newline to the end of a line in an existing index file #1875 (#1876) (727cbb5)
  • core: make sure to only handle first tag when grouping (#1942) (c46f6c9)

... (truncated)

Commits
  • 5fa09bb chore(release): 7.8.0
  • 9185b97 fix(zod): correct tuple function mapping (#2006)
  • 994cc86 feat(core): add support for more enumname extensions (#2005)
  • 1881dfa fix(zod): handle $ref property names in schemas correctly (#1999)
  • 8cfb83e fix(zod): enum schema generation for various types (#1996)
  • 68dd5a5 docs(custom-client): update example to match the generated api (#1994)
  • d4c43a0 chore(deps) fix Next.js critical vulnerability (#1991)
  • ead4eb9 chore(deps): @​ibm-cloud/openapi-ruleset": "^1.29.4 (#1990)
  • e106067 feat(query): add optional queryClient argument to mutations when using TanSta...
  • 456037c feat: add optional queryClient argument (#1992)
  • Additional commits viewable in compare view

Updates vite from 4.5.5 to 6.2.5

Release notes

Sourced from vite's releases.

v6.2.5

Please refer to CHANGELOG.md for details.

v6.2.4

Please refer to CHANGELOG.md for details.

v6.2.3

Please refer to CHANGELOG.md for details.

v6.2.2

Please refer to CHANGELOG.md for details.

create-vite@6.2.1

Please refer to CHANGELOG.md for details.

v6.2.1

Please refer to CHANGELOG.md for details.

create-vite@6.2.0

Please refer to CHANGELOG.md for details.

v6.2.0

Please refer to CHANGELOG.md for details.

v6.2.0-beta.1

Please refer to CHANGELOG.md for details.

v6.2.0-beta.0

Please refer to CHANGELOG.md for details.

v6.1.4

Please refer to CHANGELOG.md for details.

v6.1.3

Please refer to CHANGELOG.md for details.

v6.1.2

Please refer to CHANGELOG.md for details.

create-vite@6.1.1

Please refer to CHANGELOG.md for details.

v6.1.1

Please refer to CHANGELOG.md for details.

create-vite@6.1.0

Please refer to CHANGELOG.md for details.

v6.1.0

Please refer to CHANGELOG.md for details.

... (truncated)

Changelog

Sourced from vite's changelog.

6.2.5 (2025-04-03)

6.2.4 (2025-03-31)

6.2.3 (2025-03-24)

6.2.2 (2025-03-14)

  • fix: await client buildStart on top level buildStart (#19624) (b31faab), closes #19624
  • fix(css): inline css correctly for double quote use strict (#19590) (d0aa833), closes #19590
  • fix(deps): update all non-major dependencies (#19613) (363d691), closes #19613
  • fix(indexHtml): ensure correct URL when querying module graph (#19601) (dc5395a), closes #19601
  • fix(preview): use preview https config, not server (#19633) (98b3160), closes #19633
  • fix(ssr): use optional chaining to prevent "undefined is not an object" happening in `ssrRewriteStac (4309755), closes #19612
  • feat: show friendly error for malformed base (#19616) (2476391), closes #19616
  • feat(worker): show asset filename conflict warning (#19591) (367d968), closes #19591
  • chore: extend commit hash correctly when ambigious with a non-commit object (#19600) (89a6287), closes #19600

6.2.1 (2025-03-07)

... (truncated)

Commits

You can trigger a rebase of this PR 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

…d vite

Bumps [esbuild](https://github.com/evanw/esbuild) to 0.25.2 and updates ancestor dependencies [esbuild](https://github.com/evanw/esbuild), [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest), [@vitejs/plugin-react-swc](https://github.com/vitejs/vite-plugin-react-swc), [orval](https://github.com/orval-labs/orval) and [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite). These dependencies need to be updated together.


Updates `esbuild` from 0.19.8 to 0.25.2
- [Release notes](https://github.com/evanw/esbuild/releases)
- [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG-2023.md)
- [Commits](evanw/esbuild@v0.19.8...v0.25.2)

Updates `vitest` from 0.34.6 to 3.1.1
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Commits](https://github.com/vitest-dev/vitest/commits/v3.1.1/packages/vitest)

Updates `@vitejs/plugin-react-swc` from 3.5.0 to 3.8.1
- [Release notes](https://github.com/vitejs/vite-plugin-react-swc/releases)
- [Changelog](https://github.com/vitejs/vite-plugin-react-swc/blob/main/CHANGELOG.md)
- [Commits](vitejs/vite-plugin-react-swc@v3.5.0...v3.8.1)

Updates `orval` from 6.22.1 to 7.8.0
- [Release notes](https://github.com/orval-labs/orval/releases)
- [Changelog](https://github.com/orval-labs/orval/blob/master/.release-it.json)
- [Commits](orval-labs/orval@v6.22.1...v7.8.0)

Updates `vite` from 4.5.5 to 6.2.5
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v6.2.5/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v6.2.5/packages/vite)

---
updated-dependencies:
- dependency-name: esbuild
  dependency-version: 0.25.2
  dependency-type: indirect
- dependency-name: vitest
  dependency-version: 3.1.1
  dependency-type: direct:development
- dependency-name: "@vitejs/plugin-react-swc"
  dependency-version: 3.8.1
  dependency-type: direct:development
- dependency-name: orval
  dependency-version: 7.8.0
  dependency-type: direct:development
- dependency-name: vite
  dependency-version: 6.2.5
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Apr 7, 2025
@complianator-bot
Copy link

Metadata Validation Result

FYI: your catalog-info.yaml contains errors.

Why is this popping up?
  • We want to ensure each software and infrastructure component in the 1K5 org is catalogued.
  • This helps us to better identify ownership, understand relations and resolve incidents.
  • Therefore, each repository must contain a catalog-info.yaml that includes a description, type, owner, lifecycle and corresponding system.
  • The Complianator Bot informs teams about missing / invalid properties in their catalog-info.yaml in Pull Requests (right now, only as a non-breaking warning).
  • You can find a list of your team's components in DevHub.
  • Check the metadata guide for detailed information
Line number (click to edit) Error ToDo
0 catalog-info..yaml missing.` Please create a valid catalog-info.yaml following this documentation.

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

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant