chore(deps): bump the production-dependencies group with 4 updates

[dependabot]

Bumps the production-dependencies group with 4 updates: pixi.js, preact, @types/node and esbuild.

Updates pixi.js from 8.16.0 to 8.17.0

Release notes

Sourced from pixi.js's releases.

v8.17.0

💾 Download

Installation:

npm install pixi.js@8.17.0

Development Build:

• https://cdn.jsdelivr.net/npm/pixi.js@8.17.0/dist/pixi.js
• https://cdn.jsdelivr.net/npm/pixi.js@8.17.0/dist/pixi.mjs

Production Build:

• https://cdn.jsdelivr.net/npm/pixi.js@8.17.0/dist/pixi.min.js
• https://cdn.jsdelivr.net/npm/pixi.js@8.17.0/dist/pixi.min.mjs

Documentation:

• https://pixijs.download/v8.17.0/docs/index.html

Changed

pixijs/pixijs@v8.16.0...v8.17.0

🚨 Behavior Change

• BlurFilter now uses an optimized halving strength scheme by default, which changes visual output compared to previous versions. Set legacy: true to restore the old behavior.

  new BlurFilter({ legacy: true });
  // or globally:
  BlurFilter.defaultOptions.legacy = true;

• Text with align: 'justify' now uses wordWrapWidth for width calculation instead of maxLineWidth, matching CSS behavior. The last line is no longer stretched.
• breakWords: true in HTMLText now correctly uses CSS word-break: break-word instead of break-all to match behavior of other text renderers.

🎁 Added

• feat: add tagged text support to canvasTextSplit by @​Zyie in pixijs/pixijs#11949
  • SplitText now supports tagStyles, so styled runs (e.g. <red>Hello</red> <blue>World</blue>) are correctly split into per-character Text objects with individual styles preserved.
• feat: Improves text rendering and layout handling by @​Zyie in pixijs/pixijs#11947
  • Bitmap text now supports whiteSpace modes (normal, pre, nowrap, pre-line, pre-wrap) with proper space/newline collapsing
  • Bitmap text word wrap supports break-after characters (hyphens, en-dash, em-dash, soft hyphen)
  • Canvas text and split text now render align: 'justify' by distributing extra word spacing
  • Dynamic bitmap fonts scale drop shadow blur and distance proportionally to font size
  • Bitmap font xAdvance now uses true advance width from measureText() instead of bounding-box width
  • Kerning values correctly scaled by fontScale in dynamic bitmap fonts
• feat: add visibleChanged event to container by @​ikigai-bjorn-s in pixijs/pixijs#11940

  container.on('visibleChanged', (visible) => {
      console.log('Visibility changed to:', visible);
  });

• feat: Add function for removing aliases from resolver by @​Sertion in pixijs/pixijs#11921

... (truncated)

Commits

• 4806c3b v8.17.0
• 6e9619d feat: add tagged text support to canvasTextSplit (#11949)
• 128ab8a docs: expand build, test, and API documentation (#11956)
• 4f3c960 chore: add titles to visual test diff snapshots (#11954)
• c450e9a feat: Improves text rendering and layout handling (#11947)
• c877399 fix: move DOMPipe extension registration back to init.ts (#11953)
• 3878d00 fix: removeAllListeners() on Renderer.destroy() (#11951)
• fb8f8bb fix: correct minFPS/maxFPS mutual clamping in Ticker (#11952)
• c24a9ca fix: return valid empty bounds from empty Graphics (#11908)
• aa6045d documentation updated (#11935)
• Additional commits viewable in compare view

Updates preact from 10.28.4 to 10.29.0

Release notes

Sourced from preact's releases.

10.29.0

Features

• Implement flushSync (#5036, thanks @​JoviDeCroock)

Fixes

• Ensure we reset renderCount (#5017, thanks @​JoviDeCroock)
• undefined prototype (#5041, thanks @​JoviDeCroock)

Performance

• Golf down compat (#5025, thanks @​JoviDeCroock)

Commits

• 6ef4405 10.29.0 (#5052)
• 55254ef Ensure we reset renderCount (#5017)
• b341bfe undefined prototype (#5041)
• 978c0b9 Implement flushSync (#5036)
• af4c459 Golf down compat (#5025)
• See full diff in compare view

Updates @types/node from 25.3.5 to 25.5.0

Commits

• See full diff in compare view

Updates esbuild from 0.27.3 to 0.27.4

Release notes

Sourced from esbuild's releases.

v0.27.4

• Fix a regression with CSS media queries (#4395, #4405, #4406)

  Version 0.25.11 of esbuild introduced support for parsing media queries. This unintentionally introduced a regression with printing media queries that use the <media-type> and <media-condition-without-or> grammar. Specifically, esbuild was failing to wrap an or clause with parentheses when inside <media-condition-without-or>. This release fixes the regression.

  Here is an example:

  /* Original code */
  @media only screen and ((min-width: 10px) or (min-height: 10px)) {
    a { color: red }
  }
  /* Old output (incorrect) */
  @​media only screen and (min-width: 10px) or (min-height: 10px) {
  a {
  color: red;
  }
  }
  /* New output (correct) */
  @​media only screen and ((min-width: 10px) or (min-height: 10px)) {
  a {
  color: red;
  }
  }

• Fix an edge case with the inject feature (#4407)

  This release fixes an edge case where esbuild's inject feature could not be used with arbitrary module namespace names exported using an export {} from statement with bundling disabled and a target environment where arbitrary module namespace names is unsupported.

  With the fix, the following inject file:

  import jquery from 'jquery';
  export { jquery as 'window.jQuery' };

  Can now always be rewritten as this without esbuild sometimes incorrectly generating an error:

  export { default as 'window.jQuery' } from 'jquery';

• Attempt to improve API handling of huge metafiles (#4329, #4415)

  This release contains a few changes that attempt to improve the behavior of esbuild's JavaScript API with huge metafiles (esbuild's name for the build metadata, formatted as a JSON object). The JavaScript API is designed to return the metafile JSON as a JavaScript object in memory, which makes it easy to access from within a JavaScript-based plugin. Multiple people have encountered issues where this API breaks down with a pathologically-large metafile.

  The primary issue is that V8 has an implementation-specific maximum string length, so using the JSON.parse API with large enough strings is impossible. This release will now attempt to use a fallback JavaScript-based JSON parser that operates directly on the UTF8-encoded JSON bytes instead of using JSON.parse when the JSON metafile is too big to fit in a JavaScript string. The new fallback path has not yet been heavily-tested. The metafile will also now be generated with whitespace removed if the bundle is significantly large, which will reduce the size of the metafile JSON slightly.

... (truncated)

Changelog

Sourced from esbuild's changelog.

0.27.4

• Fix a regression with CSS media queries (#4395, #4405, #4406)

  Version 0.25.11 of esbuild introduced support for parsing media queries. This unintentionally introduced a regression with printing media queries that use the <media-type> and <media-condition-without-or> grammar. Specifically, esbuild was failing to wrap an or clause with parentheses when inside <media-condition-without-or>. This release fixes the regression.

  Here is an example:

  /* Original code */
  @media only screen and ((min-width: 10px) or (min-height: 10px)) {
    a { color: red }
  }
  /* Old output (incorrect) */
  @​media only screen and (min-width: 10px) or (min-height: 10px) {
  a {
  color: red;
  }
  }
  /* New output (correct) */
  @​media only screen and ((min-width: 10px) or (min-height: 10px)) {
  a {
  color: red;
  }
  }

• Fix an edge case with the inject feature (#4407)

  This release fixes an edge case where esbuild's inject feature could not be used with arbitrary module namespace names exported using an export {} from statement with bundling disabled and a target environment where arbitrary module namespace names is unsupported.

  With the fix, the following inject file:

  import jquery from 'jquery';
  export { jquery as 'window.jQuery' };

  Can now always be rewritten as this without esbuild sometimes incorrectly generating an error:

  export { default as 'window.jQuery' } from 'jquery';

• Attempt to improve API handling of huge metafiles (#4329, #4415)

  This release contains a few changes that attempt to improve the behavior of esbuild's JavaScript API with huge metafiles (esbuild's name for the build metadata, formatted as a JSON object). The JavaScript API is designed to return the metafile JSON as a JavaScript object in memory, which makes it easy to access from within a JavaScript-based plugin. Multiple people have encountered issues where this API breaks down with a pathologically-large metafile.

... (truncated)

Commits

• f9c9012 publish 0.27.4 to npm
• 207dbc7 js api: fall back to js-based metafile json parser
• 1ca56dc fix #4329: auto-minify metafile for large bundles
• e3823aa fix #4415: add uint cast to stdio int parser
• d50e88c chore: correct copy&paste panic message (#4399)
• 8b829b1 fix #4407: incorrect error for inject edge case
• 4384bad fix #4395 close #4405 close #4406: parens for or
• See full diff 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 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

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.