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

• Fix incorrect paths in inline source maps (#4070, #4075, #4105)

... (truncated)

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)

• 4475787 publish 0.25.2 to npm
• 8f56771 fix #4121: map js regexp flags to go regexp flags
• 36b458d follow-up to #4109
• 8b8437c feat: support index source map (#4109)
• 75286c1 unit test for absolute windows paths in source map
• bcc77fb fix #4100: invalid identifiers in node annotation
• 37cb6a2 fix a warning from npm publish
• 6bfc1c1 publish 0.25.1 to npm
• f9b3952 fix #4078: prepend namespaces to source map paths
• ccf3dd7 add "contributed by" in changelog
• Additional commits viewable in compare view

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

plugin-react@4.4.1

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

plugin-react@4.4.0

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.

plugin-react@4.4.0-beta.2

Add reactRefreshHost option

Add reactRefreshHost option to set a React Fast Refresh runtime URL prefix. This is useful in a module federation context to enable HMR by specifying the host application URL in the Vite config of a remote application. See full discussion here: module-federation/vite#183

export default defineConfig({
  plugins: [react({ reactRefreshHost: 'http://localhost:3000' })],
})

plugin-react@4.4.0-beta.1

No release notes provided.

plugin-react@4.3.4

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

plugin-react@4.3.3

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

npm install babel-plugin-react-compiler react-compiler-runtime @babel/plugin-transform-react-jsx-development

</tr></table> 

... (truncated)

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

4.4.1 (2025-04-19)

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

4.4.0 (2025-04-15)

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.

4.4.0-beta.2 (2025-04-15)

Add reactRefreshHost option

Add reactRefreshHost option to set a React Fast Refresh runtime URL prefix. This is useful in a module federation context to enable HMR by specifying the host application URL in the Vite config of a remote application. See full discussion here: module-federation/vite#183

export default defineConfig({
  plugins: [react({ reactRefreshHost: 'http://localhost:3000' })],
})

4.4.0-beta.1 (2025-04-09)

4.4.0-beta.0 (2025-04-09)

4.3.4 (2024-11-26)

Add Vite 6 to peerDependencies range

Vite 6 is highly backward compatible, not much to add!

Force Babel to output spec compliant import attributes #386

The default was an old spec (with type: "json"). We now enforce spec compliant (with { type: "json" })

4.3.3 (2024-10-19)

React Compiler runtimeModule option removed

React Compiler was updated to accept a target option and runtimeModule was removed. vite-plugin-react will still detect runtimeModule for backwards compatibility.

When using a custom runtimeModule or target !== '19', the plugin will not try to pre-optimize react/compiler-runtime dependency.

The react-compiler-runtime is now available on npm can be used instead of the local shim for people using the compiler with React < 19.

Here is the configuration to use the compiler with React 18 and correct source maps in development:

... (truncated)

• 57cc398 release: plugin-react@4.4.1
• a62bdd6 fix(react): fix package.json types (#462)
• 8beda4f release: plugin-react@4.4.0
• fffe4ad feat: add support for rolldown-vite (#451)
• c197fd9 release: plugin-react@4.4.0-beta.2
• bd1a1ad fix(deps): update all non-major dependencies (#392)
• 87f7fdd feat: add reactRefreshHost option to support module federation HMR (#420)
• da01d56 release: plugin-react@4.4.0-beta.1
• 9b1b510 chore: fix refresh runtime path in dev (#444)
• 8258442 release: plugin-react@4.4.0-beta.0
• Additional commits viewable in compare view

Sourced from vite's releases.

v6.3.2

Please refer to CHANGELOG.md for details.

create-vite@6.3.1

Please refer to CHANGELOG.md for details.

v6.3.1

Please refer to CHANGELOG.md for details.

create-vite@6.3.0

Please refer to CHANGELOG.md for details.

v6.3.0

Please refer to CHANGELOG.md for details.

v6.3.0-beta.2

Please refer to CHANGELOG.md for details.

v6.3.0-beta.1

Please refer to CHANGELOG.md for details.

v6.3.0-beta.0

Please refer to CHANGELOG.md for details.

v6.2.6

Please refer to CHANGELOG.md for details.

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.

... (truncated)

Sourced from vite's changelog.

6.3.2 (2025-04-18)

• fix: match default asserts case insensitive (#19852) (cbdab1d), closes #19852
• fix: open first url if host does not match any urls (#19886) (6abbdce), closes #19886
• fix(css): respect css.lightningcss option in css minification process (#19879) (b5055e0), closes #19879
• fix(deps): update all non-major dependencies (#19698) (bab4cb9), closes #19698
• feat(css): improve lightningcss messages (#19880) (c713f79), closes #19880

6.3.1 (2025-04-17)

• fix: avoid using Promise.allSettled in preload function (#19805) (35c7f35), closes #19805
• fix: backward compat for internal plugin transform calls (#19878) (a152b7c), closes #19878

6.3.0 (2025-04-16)

• fix(hmr): avoid infinite loop happening with hot.invalidate in circular deps (#19870) (d4ee5e8), closes #19870
• fix(preview): use host url to open browser (#19836) (5003434), closes #19836

6.3.0-beta.2 (2025-04-11)

• fix: addWatchFile doesn't work if base is specified (fixes #19792) (#19794) (8bed1de), closes #19792 #19794
• fix: correct the behavior when multiple transform filter options are specified (#19818) (7200dee), closes #19818
• fix: fs check with svg and relative paths (#19782) (62d7e81), closes #19782
• fix: keep entry asset files imported by other files (#19779) (2fa1495), closes #19779
• fix: reject requests with # in request-target (#19830) (175a839), closes #19830
• fix: unbundle fdir to fix commonjsOptions.dynamicRequireTargets (#19791) (71227be), closes #19791
• fix(css): remove empty chunk imports correctly when chunk file name contained special characters (#1 (b125172), closes #19814
• fix(dev): make query selector regexes more inclusive (fix #19213) (#19767) (f530a72), closes #19213 #19767
• fix(hmr): run HMR handler sequentially (#19793) (380c10e), closes #19793
• fix(module-runner): allow already resolved id as entry (#19768) (e2e11b1), closes #19768
• fix(types): remove the keepProcessEnv from the DefaultEnvironmentOptions type (#19796) (36935b5), closes #19796
• refactor: simplify pluginFilter implementation (#19828) (0a0c50a), closes #19828
• perf(css): avoid constructing renderedModules (#19775) (59d0b35), closes #19775
• test: tweak generateCodeFrame test (#19812) (8fe3538), closes #19812
• docs(vite): fix description of transformIndexHtml hook (#19799) (a0e1a04), closes #19799
• chore: remove unused eslint directive (#19781) (cb4f5b4), closes #19781

6.3.0-beta.1 (2025-04-03)

• fix: align plugin hook filter behavior with pluginutils (#19736) (0bbdd2c), closes #19736
• fix: fs check in transform middleware (#19761) (5967313), closes #19761
• fix(hmr): throw non-standard error info causes logical error (#19776) (6b648c7), closes #19776

... (truncated)

• 4bc17b4 release: v6.3.2
• b5055e0 fix(css): respect css.lightningcss option in css minification process (#19879)
• c713f79 feat(css): improve lightningcss messages (#19880)
• cbdab1d fix: match default asserts case insensitive (#19852)
• 6abbdce fix: open first url if host does not match any urls (#19886)
• bab4cb9 fix(deps): update all non-major dependencies (#19698)
• a7349ef release: v6.3.1
• a152b7c fix: backward compat for internal plugin transform calls (#19878)
• 35c7f35 fix: avoid using Promise.allSettled in preload function (#19805)
• 5fdcfe7 release: v6.3.0
• Additional commits viewable in compare view

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.