Bump esbuild, @vitejs/plugin-react, astro and @astrojs/mdx

[dependabot]

Bumps esbuild to 0.25.12 and updates ancestor dependencies esbuild, @vitejs/plugin-react, astro and @astrojs/mdx. These dependencies need to be updated together.

Updates esbuild from 0.21.5 to 0.25.12

Release notes

Sourced from esbuild's releases.

v0.25.12

• Fix a minification regression with CSS media queries (#4315)

  The previous release introduced support for parsing media queries which unintentionally introduced a regression with the removal of duplicate media rules during minification. Specifically the grammar for @media <media-type> and <media-condition-without-or> { ... } was missing an equality check for the <media-condition-without-or> part, so rules with different suffix clauses in this position would incorrectly compare equal and be deduplicated. This release fixes the regression.

• Update the list of known JavaScript globals (#4310)

  This release updates esbuild's internal list of known JavaScript globals. These are globals that are known to not have side-effects when the property is accessed. For example, accessing the global Array property is considered to be side-effect free but accessing the global scrollY property can trigger a layout, which is a side-effect. This is used by esbuild's tree-shaking to safely remove unused code that is known to be side-effect free. This update adds the following global properties:

  From ES2017:

  • Atomics
  • SharedArrayBuffer

  From ES2020:

  • BigInt64Array
  • BigUint64Array

  From ES2021:

  • FinalizationRegistry
  • WeakRef

  From ES2025:

  • Float16Array
  • Iterator

  Note that this does not indicate that constructing any of these objects is side-effect free, just that accessing the identifier is side-effect free. For example, this now allows esbuild to tree-shake classes that extend from Iterator:

  // This can now be tree-shaken by esbuild:
  class ExampleIterator extends Iterator {}

• Add support for the new @view-transition CSS rule (#4313)

  With this release, esbuild now has improved support for pretty-printing and minifying the new @view-transition rule (which esbuild was previously unaware of):

  /* Original code */
  @view-transition {
    navigation: auto;
    types: check;
  }
  /* Old output */
  @​view-transition { navigation: auto; types: check; }
  /* New output */
  @​view-transition {
  navigation: auto;
  types: check;

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

• 208f539 publish 0.25.12 to npm
• 5f03afd update release notes
• 6b2ee78 minify: remove css rules containing empty :is()
• f361deb add some additional known static methods
• 07aa646 automatically mark "RegExp.escape()" calls as pure
• 9039c46 simplify some call expression checks
• 188944d add some additional known static methods
• d3c67f9 fix #4310: add Iterator and other known globals
• 4a51f0b fix: escape dev server breadcrumb hrefs properly (#4316)
• 26b29ed fix #4315: @media deduplication bug edge case
• Additional commits viewable in compare view

Updates @vitejs/plugin-react from 4.2.0 to 4.7.0

Release notes

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

plugin-react@4.7.0

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({ babel: { plugins: ['babel-plugin-react-compiler'] } })
  .map(p => ({ ...p, applyToEnvironment: e => e.name === 'client' }))

plugin-react@4.6.0

Add raw Rolldown support

This plugin only worked with Vite. But now it can also be used with raw Rolldown. The main purpose for using this plugin with Rolldown is to use react compiler.

plugin-react@4.5.2

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.

plugin-react@4.5.1

Add explicit semicolon in preambleCode #485

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

plugin-react@4.5.0

Add filter for rolldown-vite #470

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

... (truncated)

Changelog

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

4.7.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({ babel: { plugins: ['babel-plugin-react-compiler'] } })
  .map(p => ({ ...p, applyToEnvironment: e => e.name === 'client' }))

4.6.0 (2025-06-23)

Add raw Rolldown support

This plugin only worked with Vite. But now it can also be used with raw Rolldown. The main purpose for using this plugin with Rolldown is to use react compiler.

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

4.5.1 (2025-06-03)

Add explicit semicolon in preambleCode #485

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

4.5.0 (2025-05-23)

... (truncated)

Commits

• 8041706 release: plugin-react@4.7.0
• bbfd1b7 chore: update changelog for #537
• fdc9d9a feat: add hmr support for compound components (#518)
• d14f31d fix(deps): update all non-major dependencies (#568)
• 22be17f build: use tsdown for plugin-react / plugin-react-oxc (#554)
• 840f0b1 chore(deps): update prettier (#556)
• cfe2912 fix(deps): update all non-major dependencies (#540)
• 11f56d6 fix: return Plugin[] instead of PluginOption[] (#537)
• 9da5e19 fix(deps): update all non-major dependencies (#519)
• 1583c5d chore: remove Vite 7 beta from supported range (#517)
• Additional commits viewable in compare view

Updates astro from 4.16.19 to 5.16.12

Release notes

Sourced from astro's releases.

astro@5.16.12

Patch Changes

• #15175 47ae148 Thanks @​florian-lefebvre! - Allows experimental Font providers to specify family options

  Previously, an Astro FontProvider could only accept options at the provider level when called. That could result in weird data structures for family-specific options.

  Astro FontProviders can now declare family-specific options, by specifying a generic:

  // font-provider.ts
  import type { FontProvider } from "astro";
  import { retrieveFonts, type Fonts } from "./utils.js",
  interface Config {
  token: string;
  }
  +interface FamilyOptions {
  
  minimal?: boolean;
  +}
  
  -export function registryFontProvider(config: Config): FontProvider {
  +export function registryFontProvider(config: Config): FontProvider<FamilyOptions> {
  let data: Fonts = {}
  return {
  name: "registry",
  config,
  init: async () => {
  data = await retrieveFonts(token);
  },
  listFonts: () => {
  return Object.keys(data);
  },
  
  resolveFont: ({ familyName, ...rest }) => {
  
  
  // options is typed as FamilyOptions
  resolveFont: ({ familyName, options, ...rest }) => {
  const fonts = data[familyName];
  if (fonts) {
  return { fonts };
  }
  return undefined;
  },
  };
  }

Once the font provider is registered in the Astro config, types are automatically inferred:

... (truncated)

Changelog

Sourced from astro's changelog.

5.16.12

Patch Changes

• #15175 47ae148 Thanks @​florian-lefebvre! - Allows experimental Font providers to specify family options

  Previously, an Astro FontProvider could only accept options at the provider level when called. That could result in weird data structures for family-specific options.

  Astro FontProviders can now declare family-specific options, by specifying a generic:

  // font-provider.ts
  import type { FontProvider } from "astro";
  import { retrieveFonts, type Fonts } from "./utils.js",
  interface Config {
  token: string;
  }
  +interface FamilyOptions {
  
  minimal?: boolean;
  +}
  
  -export function registryFontProvider(config: Config): FontProvider {
  +export function registryFontProvider(config: Config): FontProvider<FamilyOptions> {
  let data: Fonts = {}
  return {
  name: "registry",
  config,
  init: async () => {
  data = await retrieveFonts(token);
  },
  listFonts: () => {
  return Object.keys(data);
  },
  
  resolveFont: ({ familyName, ...rest }) => {
  
  
  // options is typed as FamilyOptions
  resolveFont: ({ familyName, options, ...rest }) => {
  const fonts = data[familyName];
  if (fonts) {
  return { fonts };
  }
  return undefined;
  },
  };
  }

Once the font provider is registered in the Astro config, types are automatically inferred:

... (truncated)

Commits

• dc5bcd9 [ci] release (#15228)
• 47ae148 feat(fonts)!: family options (#15175)
• c0595b3 feat(fonts)!: fontData instead of getFontData() (#15200)
• 096c331 fix: typo in comment (#15232)
• 2a6315a React / MDX nested regression (#15253)
• 731f52d fix: prevent font copying when stopping dev server with q+enter (#15178)
• 8d84b30 bug: Support remote url for css in content collection (#15254)
• 3da6272 Fix greedy regex in error message markdown rendering (#15230)
• c390fb7 refactor(fonts): use runtime as entrypoint (#15181)
• 1a3f302 refactor(fonts): do not mutate provider name (#15190)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.

Updates @astrojs/mdx from 3.1.8 to 4.3.13

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​4.3.13

Patch Changes

• Updated dependencies [d8305f8]:
  • @​astrojs/markdown-remark@​6.3.10

@​astrojs/mdx@​4.3.12

Patch Changes

• #14813 e1dd377 Thanks @​ematipico! - Removes picocolors as dependency in favor of the fork piccolore.

@​astrojs/mdx@​4.3.11

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.9

Changelog

Sourced from @​astrojs/mdx's changelog.

4.3.13

Patch Changes

• Updated dependencies [d8305f8]:
  • @​astrojs/markdown-remark@​6.3.10

4.3.12

Patch Changes

• #14813 e1dd377 Thanks @​ematipico! - Removes picocolors as dependency in favor of the fork piccolore.

4.3.11

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.9

4.3.10

Patch Changes

• #14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

  The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

  See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

4.3.9

Patch Changes

• #14621 e3175d9 Thanks @​GameRoMan! - Updates vite version to fix CVE

4.3.8

Patch Changes

• #14591 3e887ec Thanks @​matthewp! - Adds TypeScript support for the components prop on MDX Content component when using await render(). Developers now get proper IntelliSense and type checking when passing custom components to override default MDX element rendering.

• #14598 7b45c65 Thanks @​delucis! - Reduces terminal text styling dependency size by switching from kleur to picocolors

4.3.7

Patch Changes

• Updated dependencies []:
  • @​astrojs/markdown-remark@​6.3.8

... (truncated)

Commits

• 02c19eb [ci] release (#14959)
• e878679 [ci] release (#14808)
• e1dd377 fix: remove picocolors (#14813)
• 7a07f02 [ci] release (#14788)
• 5bc37fd fix(deps): update astro dependencies (#14739)
• 7a5f280 [ci] release (#14702)
• 3d55c5d feat: return clientEntrypoint from getContainerRenderer (#14715)
• eb8aa77 [ci] release (#14630)
• e3175d9 Update vite (#14621)
• 54803d7 [ci] release (#14603)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​astrojs/mdx since your current version.

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