Bump the production-dependencies group across 1 directory with 16 updates
Type: Pull Request
State: Closed
Association: None
Comments: 1
(6 months ago)
(6 months ago)
(6 months ago)
dependencies javascript
Bumps the production-dependencies group with 16 updates in the / directory:
| Package | From | To |
|---|---|---|
| @floating-ui/dom | 1.7.2 |
1.7.4 |
| @napi-rs/simple-git | 0.1.21 |
0.1.22 |
| ansi-truncate | 1.2.0 |
1.4.0 |
| flexsearch | 0.7.43 |
0.8.212 |
| is-absolute-url | 4.0.1 |
5.0.0 |
| pixi.js | 8.11.0 |
8.13.2 |
| preact | 10.27.0 |
10.27.2 |
| preact-render-to-string | 6.5.13 |
6.6.1 |
| pretty-bytes | 7.0.0 |
7.0.1 |
| satori | 0.16.1 |
0.18.2 |
| shiki | 1.26.2 |
3.12.2 |
| workerpool | 9.3.3 |
9.3.4 |
| @types/node | 24.1.0 |
24.4.0 |
| esbuild | 0.25.8 |
0.25.9 |
| tsx | 4.20.3 |
4.20.5 |
| typescript | 5.8.3 |
5.9.2 |
Updates @floating-ui/dom from 1.7.2 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
@floating-ui/dom@1.7.3Patch Changes
- Update dependencies:
@floating-ui/core@1.7.3
Changelog
Sourced from @floating-ui/dom's changelog.
1.7.4
Patch Changes
- fix(getViewportRect): account for space left by
scrollbar-gutter: stable1.7.3
Patch Changes
- Update dependencies:
@floating-ui/core@1.7.3
Commits
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.2.0 to 1.4.0
Commits
38cd205Bumped version to 1.4.034d2740Added support for truncating hyperlinks too6621510Bumped version to 1.3.0cb6e78cUpdated some dependencies- See full diff in compare view
Updates flexsearch from 0.7.43 to 0.8.212
Release notes
Sourced from flexsearch's releases.
v0.8.2
- Config-Serialized Query Caches, Improved caching strategy for Document indexes and Resolver
- Resolver Async Processing Workflow (including Queuing)
- Extended Resolver Support: Worker, Persistent, Cache
- Extended Result Highlighting: Boundaries, Ellipsis, Alignment
- Improved TypeScript Typings
- Improved Stemmer Handling
- Improved Result Highlighting
- Use multi-language charset normalization as the default Encoder
- Simplified charset support for multi-language content
- Charset renamed LatinExact => Exact, LatinDefault => Default and LatinSimple => Normalize, these are universal charset presets for any languages
- Charset ArabicDefault and CyrillicDefault was removed, they are fully covered by the default universal charset presets
- Charset Charset.CjkDefault was renamed to Charset.CJK
v0.8.1
- Resolver Support for Documents
- Asynchronous Runtime Balancer, new option
priority- Export/Import Worker Indexes + Document Worker, new extern config options
exportandimport- Improved interoperability of the different build packages, including source folder
- Support custom
filterfunction for encoder (stop-word filter)v0.8.0
- Persistent indexes support for:
IndexedDB(Browser),Redis,SQLite,Postgres,MongoDB,Clickhouse- Enhanced language customization via the new
Encoderclass- Result Highlighting
- Query performance achieve results up to 4.5 times faster compared to the previous generation v0.7.x by also improving the quality of results
- Enhanced support for larger indexes or larger result sets
- Improved offset and limit processing achieve up to 100 times faster traversal performance through large datasets
- Support for larger In-Memory index with extended key size (the defaults maximum keystore limit is: 2^24)
- Greatly enhanced performance of the whole text encoding pipeline
- Improved indexing of numeric content (Triplets)
- Intermediate result sets and
Resolver- Basic Resolver:
and,or,xor,not,limit,offset,boost,resolve- Improved charset collection
- New charset preset
soundexwhich further reduces memory consumption by also increasing "fuzziness"- Performance gain when polling tasks to the index by using "Event-Loop-Caches"
- Up to 100 times faster deletion/replacement when not using the additional "fastupdate" register
- Regex Pre-Compilation (transforms hundreds of regex rules into just a few)
- Extended support for multiple tags (DocumentIndex)
- Custom Fields ("Virtual Fields")
- Custom Filter
- Custom Score Function
- Added French language preset (stop-word filter, stemmer)
- Enhanced Worker Support
- Export / Import index in chunks
- Improved Build System + Bundler (Supported: CommonJS, ESM, Global Namespace), also the import of language packs are now supported for Node.js
- Full covering index.d.ts type definitions
- Fast-Boot Serialization optimized for Server-Side-Rendering (PHP, Python, Ruby, Rust, Java, Go, Node.js, ...)
Changelog
Sourced from flexsearch's changelog.
Changelog
Current Version
- Calling
index.clear()on a persistent Index does not stack to the task queue by default (which executes on commit), instead it will execute immediately and return a Promise- Added new tokenizer
tolerant, inherits fromstrictbut also matches simple typos like missing letters and swapped letters- Improved Redis Cleanup
- Resolver: Support Result Highlighting
v0.8.2
- Config-Serialized Query Caches, Improved caching strategy for Document indexes and Resolver
- Resolver Async Processing Workflow (including Queuing)
- Extended Resolver Support: Worker, Persistent, Cache
- Extended Result Highlighting: Boundaries, Ellipsis, Alignment
- Improved TypeScript Typings
- Improved Stemmer Handling
- Improved Result Highlighting
- Use multi-language charset normalization as the default
Encoder- Simplified charset support for multi-language content
- Charset renamed
LatinExact=>Exact,LatinDefault=>DefaultandLatinSimple=>Normalize, these are universal charset presets for any languages- Charset
ArabicDefaultandCyrillicDefaultwas removed, they are fully covered by the default universal charset presets- Charset
Charset.CjkDefaultwas renamed toCharset.CJKv0.8.1
- Resolver Support for Documents
- Asynchronous Runtime Balancer, new option
priority- Export/Import Worker Indexes + Document Worker, new extern config options
exportandimport- Improved interoperability of the different build packages, including source folder
- Support custom
filterfunction for encoder (stop-word filter)v0.8.0
- Persistent indexes support for:
IndexedDB(Browser),Redis,SQLite,Postgres,MongoDB,Clickhouse- Enhanced language customization via the new
Encoderclass- Result Highlighting
- Query performance achieve results up to 4.5 times faster compared to the previous generation v0.7.x by also improving the quality of results
- Enhanced support for larger indexes or larger result sets
- Improved offset and limit processing achieve up to 100 times faster traversal performance through large datasets
- Support for larger In-Memory index with extended key size (the defaults maximum keystore limit is: 2^24)
- Greatly enhanced performance of the whole text encoding pipeline
- Improved indexing of numeric content (Triplets)
- Intermediate result sets and
Resolver- Basic Resolver:
and,or,xor,not,limit,offset,boost,resolve- Improved charset collection
- New charset preset
soundexwhich further reduces memory consumption by also increasing "fuzziness"- Performance gain when polling tasks to the index by using "Event-Loop-Caches"
- Up to 100 times faster deletion/replacement when not using the additional "fastupdate" register
- Regex Pre-Compilation (transforms hundreds of regex rules into just a few)
... (truncated)
Commits
- See full diff in compare view
Updates is-absolute-url from 4.0.1 to 5.0.0
Release notes
Sourced from is-absolute-url's releases.
v5.0.0
Breaking
- Require Node.js 20 430699d
- It now only allows
http://andhttps://protocols by default 05e1989
- To get the old behavior, pass in
{httpOnly: false}Improvements
- Add
httpOnlyoption and make it the default 05e1989
https://github.com/sindresorhus/is-absolute-url/compare/v4.0.1...v5.0.0
Commits
76c6aff5.0.005e1989AddhttpOnlyoption and make it the default430699dRequire Node.js 20- See full diff in compare view
Updates pixi.js from 8.11.0 to 8.13.2
Release notes
Sourced from pixi.js's releases.
v8.13.2
💾 Download
Installation:
npm install pixi.js@8.13.2Development Build:
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.2/dist/pixi.js
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.2/dist/pixi.mjs
Production Build:
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.2/dist/pixi.min.js
- https://cdn.jsdelivr.net/npm/pixi.js@8.13.2/dist/pixi.min.mjs
Documentation:
Changed
https://github.com/pixijs/pixi.js/compare/v8.13.1...v8.13.2
🐛 Fixed
- fix: application destroy for graphics by
@Zyiein pixijs/pixijs#11659- fix: recalculate the boundaries of
GraphicsContextregardless of renderingdirtystate by@mayakwdin pixijs/pixijs#11671- fix: destroy of prepared but not rendered text should not throw an error by
@mayakwdin pixijs/pixijs#11672v8.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
... (truncated)
Commits
8eee29cv8.13.22fd06dcfix: application destroy for graphics (#11659)f3ed022fix: recalculate the boundaries ofGraphicsContextregardless of rendering ...fbf2049fix: destroy of prepared but not rendered text should not throw an error (#11...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)- Additional commits viewable in compare view
Updates preact from 10.27.0 to 10.27.2
Release notes
Sourced from preact's releases.
10.27.2
Types
- Mirror non-JSX types to the 'preact' namespace (#4904, thanks
@rschristian)Fixes
- Address memory leak (#4906, thanks
@JoviDeCroock)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
0dbe63610.27.2 (#4917)b0cb7c5ci: Revert #4911 (#4912)3e86d02ci: Kickstart benches again in v10.x w/ successful run (#4911)0be5d20refactor (v10): Mirror non-JSX types to the 'preact' namespace (#4904)a1039ccPrevent frequently updated components from retaining memory (#4906)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-field- Additional commits viewable 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 pretty-bytes from 7.0.0 to 7.0.1
Release notes
Sourced from pretty-bytes's releases.
v7.0.1
- Fix precision with the
binaryoption (#88) c9fd951
https://github.com/sindresorhus/pretty-bytes/compare/v7.0.0...v7.0.1
Commits
3c77fd17.0.1c9fd951Fix precision with thebinaryoption (#88)4186190Fix CI- See full diff in compare view
Updates satori from 0.16.1 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
- added obj fit to image (#703) (4a7d0bc)
- Standalone build to support providing WASM binary manually (#705) (f24d911), closes #693
0.16.2
0.16.2 (2025-07-29)
Bug Fixes
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)3262159fix: zero value should make sense (#696)- See full diff in compare view
Updates shiki from 1.26.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
v3.9.2
🚀 Features
- Add funding buttons to themes & languages list - by
@jtbandesand@antfuin shikijs/shiki#1052 (84a65)- Allow negative character positions for denoting end of line offsets - by
@sealer3and@antfuin shikijs/shiki#1051 (af44b)View changes on GitHub
v3.9.1
🚀 Features
... (truncated)
Commits
e462618chore: release v3.12.2793d71echore: release v3.12.19260f3fchore: release v3.12.0d05f39bchore: release v3.11.0bda1a76chore: release v3.10.009921f1chore: release v3.9.2854eddfchore: release v3.9.1950ede5chore: release v3.9.0b92e07bchore: release v3.8.14431931chore: release v3.8.0- 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 shiki since your current version.
Updates workerpool from 9.3.3 to 9.3.4
Changelog
Sourced from workerpool's changelog.
2025-09-10, version 9.3.4
- Fix: #516 improve error handling for errors containing nested classes by using their
.toJSONmethod when available.
Commits
- See full diff in compare view
Updates @types/node from 24.1.0 to 24.4.0
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.3 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:
v4.20.4
4.20.4 (2025-08-12)
Bug Fixes
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 conditiona639836fix: override Node's native TS formats (#733)- Additional commits viewable in compare view
Updates typescript from 5.8.3 to 5.9.2
Release notes
Sourced from typescript's releases.
TypeScript 5.9
For release notes, check out the release announcement
- fixed issues query for Typescript 5.9.0 (Beta).
- fixed issues query for Typescript 5.9.1 (RC).
- No specific changes for TypeScript 5.9.2 (Stable)
Downloads are available on:
TypeScript 5.9 RC
For release notes, check out the release announcement
Downloads are available on:
TypeScript 5.9 Beta
For release notes, check out the release announcement.
Downloads are available on:
Pull Request Statistics
1
2
+372
-326
Package Dependencies
Technical Details
| ID: | 7749693 |
| UUID: | 2828280280 |
| Node ID: | PR_kwDOPU-37s6olCHY |
| Host: | GitHub |
| Repository: | devidd22/Blog-Learning-Scripting |
| Mergeable: | Yes |
| Merge State: | Clean |