chore(deps): bump the production-dependencies group across 1 directory with 12 updates
Type: Pull Request
State: Closed
Association: Contributor
Comments: 2
(3 months ago)
(3 months ago)
(3 months ago)
dependencies javascript
Bumps the production-dependencies group with 12 updates in the / directory:
| Package | From | To |
|---|---|---|
| @floating-ui/dom | 1.7.3 |
1.7.4 |
| @napi-rs/simple-git | 0.1.21 |
0.1.22 |
| ansi-truncate | 1.3.0 |
1.4.0 |
| flexsearch | 0.8.205 |
0.8.212 |
| pixi.js | 8.12.0 |
8.13.1 |
| preact | 10.27.0 |
10.27.1 |
| preact-render-to-string | 6.5.13 |
6.6.1 |
| satori | 0.16.2 |
0.18.2 |
| shiki | 3.9.2 |
3.12.2 |
| @types/node | 24.2.1 |
24.3.1 |
| esbuild | 0.25.8 |
0.25.9 |
| tsx | 4.20.4 |
4.20.5 |
Updates @floating-ui/dom from 1.7.3 to 1.7.4
Release notes
Sourced from @floating-ui/dom's releases.
@floating-ui/dom@1.7.4Patch Changes
- fix(getViewportRect): account for space left by
scrollbar-gutter: stable
Changelog
Sourced from @floating-ui/dom's changelog.
1.7.4
Patch Changes
- fix(getViewportRect): account for space left by
scrollbar-gutter: stable
Commits
7c33a3dchore: version packages (#3388)8b34295fix(getViewportRect): account forscrollbar-gutter: stablespace (#3387)- See full diff in compare view
Updates @napi-rs/simple-git from 0.1.21 to 0.1.22
Release notes
Sourced from @napi-rs/simple-git's releases.
v0.1.22
What's Changed
- Replace unmaintained goto-bus-stop/setup-zig with mlugg/setup-zig action by
@Copilotin Brooooooklyn/simple-git#96- chore(deps): update actions/download-artifact action to v5 by
@renovate[bot] in Brooooooklyn/simple-git#97- chore: clippy fix and npm trusted publisher by
@Brooooooklynin Brooooooklyn/simple-git#99New Contributors
@Copilotmade their first contribution in Brooooooklyn/simple-git#96Full Changelog: https://github.com/Brooooooklyn/simple-git/compare/v0.1.21...v0.1.22
Commits
7d016070.1.225792944chore: fix preversion script6cbeb6echore: clippy fix and npm trusted publisher (#99)a1dfc9bchore(deps): update actions/download-artifact action to v5 (#97)919cd79ci: replace unmaintained goto-bus-stop/setup-zig with mlugg/setup-zig action ...- See full diff in compare view
Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @napi-rs/simple-git since your current version.
Updates ansi-truncate from 1.3.0 to 1.4.0
Commits
38cd205Bumped version to 1.4.034d2740Added support for truncating hyperlinks too- See full diff in compare view
Updates flexsearch from 0.8.205 to 0.8.212
Commits
- See full diff in compare view
Updates pixi.js from 8.12.0 to 8.13.1
Release notes
Sourced from pixi.js's releases.
v8.13.1
💾 Download
Installation:
npm install pixi.js@8.13.1Development Build:
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.1/dist/pixi.js
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.1/dist/pixi.mjs
Production Build:
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.1/dist/pixi.min.js
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.1/dist/pixi.min.mjs
Documentation:
Changed
https://github.com/pixijs/pixi.js/compare/v8.13.0...v8.13.1
🐛 Fixed
- fix: text texture incorrectly released when destroyed by
@Zyiein pixijs/pixijs#11658- fix: fix accessibility debug div tabIndex label (#11654) by
@brentmcin pixijs/pixijs#11655New Contributors
@brentmcmade their first contribution in pixijs/pixijs#11655v8.13.0
💾 Download
Installation:
npm install pixi.js@8.13.0Development Build:
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.0/dist/pixi.js
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.0/dist/pixi.mjs
Production Build:
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.0/dist/pixi.min.js
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.0/dist/pixi.min.mjs
Documentation:
Changed
... (truncated)
Commits
f601213v8.13.119c6148fix: fix accessibility debug div tabIndex label (#11654) (#11655)e8814f8fix: text texture incorrectly released when destroyed (#11658)2094ca5v8.13.0e301117feat: simplified caching for text (#11505)6aeb34afix: memory leaks in renderer systems (#11581)4c7875dFix unsafe-eval particle update polyfill (#11643)3525c43fix: restorebuildGeometryFromPathfunctionality (#11623)25676edchore: add huskyrc to run without path (#11638)81a085afeat: add LRU cache for text measuring (#11644)- Additional commits viewable in compare view
Updates preact from 10.27.0 to 10.27.1
Release notes
Sourced from preact's releases.
10.27.1
Performance
- Avoid re-inserting children during bailout (#4890, thanks
@vasylenkoval)Types
- add missing React.Key (#4864, thanks
@shyguy1412)- make React.SVGAttributes generic (#4863, thanks
@shyguy1412)Fixes
- Add
.renderproperty referencing original render function (#4870, thanks@upupming)- Add
.typeproperty referencing original component (#4869, thanks@upupming)Maintenance
- Fix benchmarks for v10.x (#4891, thanks
@rschristian)- Correct contributing docs (#4861, thanks
@JoviDeCroock)
Commits
02b52e610.27.1 (#4892)28a56caci: Fix benchmarks workflow for v10.x (#4891)d92da32Port #4888 to v10 (#4890)89ad340Merge pull request #4870 from upupming/v10.x-forward-ref-render-fieldd698fd2Merge pull request #4869 from upupming/v10.x-memo-type-field5eada63fix(compat): add .render property referencing original render functione25d0b9feat: add .type property referencing original componentcf39a4bfix(types) preact/compat missing React.Key (#4864)058573cfix(types) make React.SVGAttributes generic (#4863)2a48070Accoutn for v10.x branch (#4861)- See full diff in compare view
Updates preact-render-to-string from 6.5.13 to 6.6.1
Release notes
Sourced from preact-render-to-string's releases.
v6.6.1
Patch Changes
- #427
f3f7aabThanks@rschristian! - Correct semver range to support beta releases of Preact v11v6.6.0
Minor Changes
- #376
81e7da3Thanks@JoviDeCroock! - Insert comment markers for suspended trees, only in renderToStringAsyncPatch Changes
#425
e750ba1Thanks@rschristian! - Expand semver range to support the upcoming v11 beta release#413
27f340bThanks@f0x52! - Fix async rendering of multiple suspended components in a single Suspense boundary#424
e7d241cThanks@JoviDeCroock! - Fix support for signals, we need to detect and unwrap the signal#423
ec0b614Thanks@JoviDeCroock! - Add support for new component bits#417
441dea2Thanks@rschristian! - Only abort/report errors fromrenderToPipeableStream()if the stream hasn't already been closed
Changelog
Sourced from preact-render-to-string's changelog.
6.6.1
Patch Changes
- #427
f3f7aabThanks@rschristian! - Correct semver range to support beta releases of Preact v116.6.0
Minor Changes
- #376
81e7da3Thanks@JoviDeCroock! - Insert comment markers for suspended trees, only in renderToStringAsyncPatch Changes
- #425
e750ba1Thanks@rschristian! - Expand semver range to support the upcoming v11 beta release
- #413
27f340bThanks@f0x52! - Fix async rendering of multiple suspended components in a single Suspense boundary
- #424
e7d241cThanks@JoviDeCroock! - Fix support for signals, we need to detect and unwrap the signal
- #423
ec0b614Thanks@JoviDeCroock! - Add support for new component bits
- #417
441dea2Thanks@rschristian! - Only abort/report errors fromrenderToPipeableStream()if the stream hasn't already been closed
Commits
a7a02d4Version Packages (#428)f3f7aabfix: Correct semver ranges for v11 beta releases (#427)abed487Version Packages (#412)7d7cc03Remove unused import (#426)a911cecMerge pull request #425 from preactjs/chore/expand-semver-for-v11e750ba1docs: Add changesetd995278chore: Expand semver range for v114a8d4a0Merge pull request #424 from preactjs/fix-signals-supporta5fc66bDucktypeec0b614Support new dirty bit (#423)- Additional commits viewable in compare view
Updates satori from 0.16.2 to 0.18.2
Release notes
Sourced from satori's releases.
0.18.2
0.18.2 (2025-09-02)
Bug Fixes
0.18.1
0.18.1 (2025-08-29)
Bug Fixes
0.18.0
0.18.0 (2025-08-28)
Features
Commits
5bcd097fix: Support passing instantiated wasm instance to init() (#709)589d9fafix: Performance improvement (#707)1a338cachore: Add benchmark script (#706)f24d911feat: Standalone build to support providing WASM binary manually (#705)4a7d0bcfeat: added obj fit to image (#703)50a7948feat: supportrepeating-radial-gradient(#697)- See full diff in compare view
Updates shiki from 3.9.2 to 3.12.2
Release notes
Sourced from shiki's releases.
v3.12.2
🐞 Bug Fixes
- twoslash: Fix
onTwoslashErrorreturn value handling - by@Karibashin shikijs/shiki#1070 (e86b0)View changes on GitHub
v3.12.1
No significant changes
View changes on GitHub
v3.12.0
🚀 Features
- vitepress-twoslash:
- Improve UX for option customization - by
@9romisein shikijs/shiki#1066 (e3cfd)- Twoslash inline type cache for markdown - by
@serkodevand@antfuin shikijs/shiki#1063 (dc7fb)🐞 Bug Fixes
- remove-notation-escape: Correct escape sequence - by
@sor4chiin shikijs/shiki#1065 (22d0c)View changes on GitHub
v3.11.0
🚀 Features
- core: Add
enforceoptions toShikiTransformer- by@serkodevand@antfuin shikijs/shiki#1062 (8ad05)View changes on GitHub
v3.10.0
🚀 Features
- Add funding links to playground - by
@jtbandesin shikijs/shiki#1054 (e36eb)View changes on GitHub
Commits
Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for shiki since your current version.
Updates @types/node from 24.2.1 to 24.3.1
Commits
- See full diff in compare view
Updates esbuild from 0.25.8 to 0.25.9
Release notes
Sourced from esbuild's releases.
v0.25.9
Better support building projects that use Yarn on Windows (#3131, #3663)
With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the
C:drive. The problem was as follows:
- Yarn in Plug'n'Play mode on Windows stores its global module cache on the
C:drive- Some developers put their projects on the
D:drive- Yarn generates relative paths that use
../..to get from the project directory to the cache directory- Windows-style paths don't support directory traversal between drives via
..(soD:\..is justD:)- I didn't have access to a Windows machine for testing this edge case
Yarn works around this edge case by pretending Windows-style paths beginning with
C:\are actually Unix-style paths beginning with/C:/, so the../..path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.Preserve parentheses around function expressions (#4252)
The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.
Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:
// Original code const fn0 = () => 0 const fn1 = (() => 1) console.log(fn0, function() { return fn1() }())// Old output
const fn0 = () => 0;
const fn1 = () => 1;
console.log(fn0, function() {
return fn1();
}());// New output
const fn0 = () => 0;
const fn1 = (() => 1);
console.log(fn0, (function() {
return fn1();
})());
Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.
Update Go from 1.23.10 to 1.23.12 (#4257, #4258)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.
Changelog
Sourced from esbuild's changelog.
0.25.9
Better support building projects that use Yarn on Windows (#3131, #3663)
With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the
C:drive. The problem was as follows:
- Yarn in Plug'n'Play mode on Windows stores its global module cache on the
C:drive- Some developers put their projects on the
D:drive- Yarn generates relative paths that use
../..to get from the project directory to the cache directory- Windows-style paths don't support directory traversal between drives via
..(soD:\..is justD:)- I didn't have access to a Windows machine for testing this edge case
Yarn works around this edge case by pretending Windows-style paths beginning with
C:\are actually Unix-style paths beginning with/C:/, so the../..path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.Preserve parentheses around function expressions (#4252)
The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.
Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:
// Original code const fn0 = () => 0 const fn1 = (() => 1) console.log(fn0, function() { return fn1() }())// Old output
const fn0 = () => 0;
const fn1 = () => 1;
console.log(fn0, function() {
return fn1();
}());// New output
const fn0 = () => 0;
const fn1 = (() => 1);
console.log(fn0, (function() {
return fn1();
})());
Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.
Update Go from 1.23.10 to 1.23.12 (#4257, #4258)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.
Commits
195e05cpublish 0.25.9 to npm3dac33ffix #3131, fix #3663: yarnpnp + windows + D drive0f2c5c8mock fs now supports multiple volumes on windows100a51esplit out yarnpnp snapshot tests13aace3removeC:assumption from windows snapshot testsf1f413ffix #4252: preserve parentheses around functions1bc8091fix #4257, close #4258: go 1.23.10 => 1.23.12bc52135move the go compiler version togo.versiona0af5d1makefile: useESBUILD_VERSIONconsistently- See full diff in compare view
Updates tsx from 4.20.4 to 4.20.5
Release notes
Sourced from tsx's releases.
v4.20.5
4.20.5 (2025-08-24)
Bug Fixes
- handle ambiguous packages (796053a)
This release is also available on:
Commits
e6d1a47docs: obfuscate aside classnamede2719dstyle: remove unused variable13f2954chore: upgrade docs deps0504525chore: upgrade manten132fdd8test: assert require.cachef057e7dtest: require loopa6f8f9frefactor: getFormat to handle all formats796053afix: handle ambiguous packages471997atest: CJS & ESM race condition- 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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
Pull Request Statistics
1
2
+274
-267
Package Dependencies
Technical Details
| ID: | 7275079 |
| UUID: | 2808539511 |
| Node ID: | PR_kwDOPcvxGM6nZul3 |
| Host: | GitHub |
| Repository: | JesperHelstrup/Jesper-Helstrup-Portfolio.github.io |
| Mergeable: | Yes |
| Merge State: | Clean |