54 minutes ago
zip.js

v2.8.47

What's Changed in v2.8.47

New features

  • New signCentralDirectory option in ZipWriter#close() to sign zip files. The function receives the raw data of the central directory records and returns the data of a digital signature record, e.g. a PKCS#7 signature, written between the central directory and the end of central directory record. The signature is exposed by the new digitalSignature property of ZipReader, along with the new directoryOffset and directoryLength properties to locate the signed data and verify it. zip.js stores the data as-is and does not implement the signature computation itself
  • New decryptCentralDirectory option in ZipReader to read zip files with an encrypted central directory, as defined in the Strong Encryption Specification of the ZIP format specification. The function receives the raw data stored in place of the central directory and the encryption metadata exposed in a DirectoryEncryptionInfo object, and returns the decrypted central directory records. Without this option, reading such zip files throws an ERR_ENCRYPTED_CENTRAL_DIRECTORY error. zip.js provides the encrypted data and the related metadata but does not implement the decryption itself
  • All the user-facing error message constants are now exported, e.g. ERR_INVALID_UID, ERR_INVALID_MSDOS_ATTRIBUTES, ERR_ENTRY_EXISTS, ERR_UNSUPPORTED_CRYPTO_API and ERR_WORKER_STARTUP_TIMEOUT. This allows comparing error.message with the constants instead of hardcoding the messages

Other changes

  • Improved browser testing, thanks to @danny0838 (#672): module import errors are now reported in the test results, and the new withStreamsPolyfill URL parameter runs the test suite with web-streams-polyfill on browsers missing TransformStream

Full Changelog: https://github.com/gildas-lormeau/zip.js/compare/v2.8.46...v2.8.47

1 hours ago
tdesign-vue-next

tdesign-vue-next@1.20.6

🌈 1.20.6 2026-08-13

🚀 Features

  • Comment: actions 支持 Function 类型,并补全 Array 中 TNode 函数节点渲染 @RSS1102 (#6915)

🐞 Bug Fixes

  • Button:
    • 移除组件不合理的默认 margin:0z-index:0 @RylanBot (common#2636)
    • 修复自定义 SVG 图标与文字之间缺少间距的问题 @xy200303 (common#2639)
    • 修复组件在 loading 状态丢失焦点的问题 @luppyw (#6912)
  • Comment: 修复操作项图标与文字未垂直居中的问题 @RSS1102 (#6915)
  • Form: 修复 triggerallrules 触发无效的问题 @RSS1102 (#6862)
  • Icon: 修复同时使用多个存在 alpha 通道的颜色填充时出现透明度重叠导致渲染不符合预期的问题 @uyarn (#6878)
  • Switch:
    • 修复 beforeChange Promise reject 产生未处理异常的问题 @kyui-azusa (#6875)
    • 修复事件监听器更新后 change 回调仍调用旧函数的问题 @engvuchen (#6914)
  • Table: 修复 1.20.4 版本后,未主动修改 row 时,污染原始数据导致取消编辑功能异常的问题 @uyarn (#6919)
  • Tabs: 修复 defaultValue0 时无法默认激活选项卡的问题 @kyui-azusa (#6866)

🚀 Features

  • Comment: Actions now support functions, and the rendering of TNode function nodes within arrays has been improved @RSS1102 (#6915)

🐞 Bug Fixes

  • Button:
    • The default margin:0 and z-index:0 values of this component have been removed @RylanBot (common#2636)
    • The issue of insufficient spacing between custom SVG icons and text has been resolved @xy200303 (common#2639)
    • The problem of the component losing focus when in the loading state has been fixed @luppyw (#6912)
  • Comment: The issue of icons and text related to actions not being vertically centered has been resolved @RSS1102 (#6915)
  • Form: The problem of rules with a trigger value of all not functioning properly has been fixed @RSS1102 (#6862)
  • Icon: The issue of unexpected rendering due to overlapping transparency when multiple colors with alpha channels are used simultaneously has been resolved @uyarn (#6878)
  • Switch:
    • The problem of unhandled exceptions occurring when the beforeChange Promise is rejected has been fixed @kyui-azusa (#6875)
    • The issue of the change callback still invoking the old function after event listeners are updated has been resolved @engvuchen (#6914)
  • Table: The problem that occurred after version 1.20.4, where failing to modify rows explicitly led to corruption of the original data and thus impaired the editing functionality, has been fixed @uyarn (#6919)
  • Tabs: The issue of tabs not being activated by default when defaultValue is set to 0 has been resolved @kyui-azusa (#6866)
1 hours ago
calendar

v3.7.0

New Features & Enhancements

Appointment Organiser

image

Booking

image

  • Appointment Schedule Plugin: Introduced the @dayflow-pro/appointment-schedule plugin for booking availability management and schedule windows. Includes comprehensive multi-language documentation (EN/ZH/JA) and interactive video demos.
  • Time Grid Background Layer APIs: Added time grid background layer slots and extension APIs (time-grid background & quick-create), allowing plugins to inject background availability layers, interactive deletion actions, and custom grid UI with accessibility support.
  • Native MouseEvent in Event Callbacks: Passed the native triggering MouseEvent to event callbacks (onEventClick, onEventContextMenu, etc.) and context menu slots for precise mouse coordinate and modifier key access.
  • Scheduling i18n: Added multi-language translation support for scheduling labels, appointment statuses, and time slot indicators.

What's Changed

Full Changelog: https://github.com/dayflow-js/calendar/compare/v3.6.0...v3.7.0

2 hours ago
zip.js

v2.8.46

What's Changed in v2.8.46

New features

  • New createWorker option in configure() to create the web workers, taking precedence over workerURI. It enables the standard bundler pattern new Worker(new URL("./zip-worker.js", import.meta.url), { type: "module" }), letting bundlers like webpack and Vite detect the worker script statically and compile it with its imports into a separate asset
  • New initWorker() function exposed by the new @zip.js/zip.js/worker entry point to write custom worker scripts. It can register alternative implementations of CompressionStream/DecompressionStream used to compress/decompress data, e.g. based on fflate, and an init hook called with the configuration, e.g. to load a WebAssembly module. The API reference of initWorker() includes a complete example based on fflate. Existing custom worker scripts relying on the initModule convention keep working
  • New @zip.js/zip.js/lib/zip-core-custom.js entry point offering the full API without embedding any web worker code or deflate implementation. Combined with createWorker and a custom worker script, the compression engine of your choice ships only once, in the worker script
  • New CompressionStreamFallback and DecompressionStreamFallback options in configure() replacing the deprecated CompressionStreamZlib and DecompressionStreamZlib options. The new names reflect the role of these implementations: the fallback used when useCompressionStream is set to false or when the Compression Streams API is unavailable

Other changes

  • New section in the documentation covering custom web workers and compression engines: https://gildas-lormeau.github.io/zip.js/#custom-workers
  • The files embedding the web worker code and the WebAssembly module are now generated with rollup plugins instead of placeholder replacements, and the development and release build configurations have been merged

Full Changelog: https://github.com/gildas-lormeau/zip.js/compare/v2.8.45...v2.8.46

3 hours ago
hono

v4.13.2

What's Changed

Full Changelog: https://github.com/honojs/hono/compare/v4.13.1...v4.13.2

3 hours ago
engine

v2.21.4

Fixes

  • Discard out of range depth in VSM shadow casters by @mvaligursky in #9124

Full Changelog: https://github.com/playcanvas/engine/compare/v2.21.3...v2.21.4

4 hours ago
router

Release 2026-08-13 10:12

Release 2026-08-13 10:12

Changes

Features

  • integrate solid v2 query (#6938) (69da50126a) by @brenelz
  • upgrade outer-devtools-core to Solid 2.0 (868d2bfbc3) by @brenelz

Fix

  • solid-router: make the global loading boundary opt-in and server/client-symmetric (#8027) (41cffa00f3) by @ryansolid
  • solid-start: resolve SSR'd lazy() client assets via vite-plugin-solid's manifest (99756c0710) by @brenelz
  • solid-router: keep Transitioner hydration ids in sync between server and client (e021c7a352) by @brenelz
  • benchmarks: Solid v2 type fixes for new benchmark scenarios (2bb318bdcf) by @brenelz
  • benchmarks: adapt new solid benchmarks from main to Solid v2 (26d94d93fc) by @brenelz
  • lockfile: restore @rspack/binding@2.0.8 platform binaries (01dbb52d06) by @brenelz
  • solid-router: resolve defaultNotFoundComponent at render time to avoid hydration desync (#7734) (f9b0e57ce0) by @brenelz
  • update solid ssr benchmark types (3fe770ad17) by @brenelz
  • solid-router-v2: use TSR_DEFERRED_PROMISE (#7532) (ff136aaea6) by @birkskyum
  • solid-router: prevent HeadContent hydration warnings (#7510) (129d043f2d) by @brenelz
  • move HydrationScript to HeadContent (#7296) (67b46d7546) by @birkskyum
  • pin solid v2 beta.6 (#7171) (85eb16c6ad) by @birkskyum
  • adjust pre-release ranges to use caret (#7130) (72ebb55236) by @birkskyum
  • better rollupOptions/rolldownOptions handling (#6990) (56e28e47ce) by @birkskyum
  • use solid v2 query pre-release (#6977) (da2b8d9e96) by @birkskyum
  • vite 8 compat (dfd64e4a08)
  • Upgrade to solid v2 beta.3 (#6943) (c3e19322e3) by @brenelz
  • more tweaks (82e6d42fec) by @brenelz
  • test (0dc0cd0b9a) by @brenelz
  • down to one failure (faa3280b98) by @brenelz
  • solid-start basic e2e (187cc84d51) by @brenelz
  • e2e tests (d026877263) by @brenelz
  • work on solid v2 upgrade (59017534d8) by @brenelz
  • build (1021e6c7d8) by @brenelz

Performance

  • solid-router: proxy-free link props in the spread hot path (#7609) (51b4bd4f37) by @brenelz

Chore

  • e2e: migrate selective-ssr pending-min route to Solid 2 onSettled (5c400bc32e) by @brenelz
  • bump @tanstack/solid-query to 6.0.0-beta.5 (#7702) (e56bb22fc3) by @brenelz
  • upgrade solid-js to 2.0.0-beta.15 (#7688) (259efbe530) by @brenelz
  • remove unneeded changesets (144ddc748e) by @brenelz
  • fix tests (545866dd47) by @brenelz
  • sync main (440a0c9270)
  • solid router v2 pre main sync (#7517) (0a7e958c80) by @brenelz
  • bump to solid v2 beta 10 (#7284) (401272e306) by @brenelz
  • solid v2 beta 8 (#7241) (b3fedfcd4e) by @brenelz
  • upgrade Solid to v2 beta.7 (#7210) (2332fb26f9) by @brenelz
  • sync main to pre-release branch (#7106) (bb6285d888) by @birkskyum
  • merge main to solid v2 (#7105) (14d39cea3e) by @birkskyum
  • bump solid-query and vite-plugin-solid (#7103) (15652a590d) by @birkskyum
  • upgrade solid to 2.0.0-beta.5 (#7102) (bf15f69973) by @brenelz
  • bump to solidjs/signals 0.13.8 (#7076) (5cdb8115df) by @brenelz
  • bump solid-query to 6.0.0-alpha.2 (#7020) (e9e805b744) by @2wheeh
  • bump solid-query to 6.0.0-alpha.1 (#7016) (0fb8dfa67b) by @birkskyum
  • sync main branch with store refactor (#7001) (72323492af) by @brenelz
  • use solid-query v6.0.0-alpha.0 (#6989) (f5023cac3d) by @birkskyum
  • bump solid-refresh, fix deepEqual (#6910) (9ce7f97ef2) by @brenelz
  • more fixes (32b9dfb25a) by @brenelz

Build

  • bundle packages with rolldown (#6931) (b95b1061d3) by @birkskyum

Packages

  • @tanstack/solid-router@2.0.0-rc.0
  • @tanstack/solid-router-devtools@2.0.0-rc.0
  • @tanstack/solid-router-ssr-query@2.0.0-rc.0
  • @tanstack/solid-start@2.0.0-rc.0
  • @tanstack/solid-start-client@2.0.0-rc.0
  • @tanstack/solid-start-server@2.0.0-rc.0
4 hours ago
router

@tanstack/solid-start@2.0.0-rc.0

Patch Changes

  • #8058 56cc90e - Upgrade solid-js and @solidjs/web to 2.0.0-rc.0, and migrate from vite-plugin-solid to its new name @solidjs/vite-plugin at 3.0.0-next.28

    vite-plugin-solid was renamed to @solidjs/vite-plugin; its final release (3.0.0-next.27) is a re-export shim over the new package. @solidjs/vite-plugin@3.0.0-next.28 requires solid-js/@solidjs/web ^2.0.0-rc.0, so the rename and the rc bump land together.

    @tanstack/router-plugin is intentionally untouched: it detects the Solid JSX plugin by its Vite plugin name (solid), which the renamed package still registers, and its vite-plugin-solid peer is optional — so it keeps working for both Solid 1 and Solid 2 consumers without a change.

    Also bumps @tanstack/solid-query and @tanstack/solid-query-devtools to ^6.0.0-rc.0 (whose peer requires solid-js >=2.0.0-rc.0), and converges @tanstack/query-core on 5.101.4solid-query depends on query-core 5.101.0, which previously resolved to a stale 5.99.0 and produced two incompatible QueryClient types.

  • Updated dependencies [56cc90e]:

    • @tanstack/solid-router@2.0.0-rc.0
    • @tanstack/solid-start-client@2.0.0-rc.0
    • @tanstack/solid-start-server@2.0.0-rc.0
4 hours ago
router

@tanstack/solid-router-ssr-query@2.0.0-rc.0

Patch Changes

  • #8058 56cc90e - Upgrade solid-js and @solidjs/web to 2.0.0-rc.0, and migrate from vite-plugin-solid to its new name @solidjs/vite-plugin at 3.0.0-next.28

    vite-plugin-solid was renamed to @solidjs/vite-plugin; its final release (3.0.0-next.27) is a re-export shim over the new package. @solidjs/vite-plugin@3.0.0-next.28 requires solid-js/@solidjs/web ^2.0.0-rc.0, so the rename and the rc bump land together.

    @tanstack/router-plugin is intentionally untouched: it detects the Solid JSX plugin by its Vite plugin name (solid), which the renamed package still registers, and its vite-plugin-solid peer is optional — so it keeps working for both Solid 1 and Solid 2 consumers without a change.

    Also bumps @tanstack/solid-query and @tanstack/solid-query-devtools to ^6.0.0-rc.0 (whose peer requires solid-js >=2.0.0-rc.0), and converges @tanstack/query-core on 5.101.4solid-query depends on query-core 5.101.0, which previously resolved to a stale 5.99.0 and produced two incompatible QueryClient types.

4 hours ago
router

@tanstack/solid-start-client@2.0.0-rc.0

Patch Changes

  • #8058 56cc90e - Upgrade solid-js and @solidjs/web to 2.0.0-rc.0, and migrate from vite-plugin-solid to its new name @solidjs/vite-plugin at 3.0.0-next.28

    vite-plugin-solid was renamed to @solidjs/vite-plugin; its final release (3.0.0-next.27) is a re-export shim over the new package. @solidjs/vite-plugin@3.0.0-next.28 requires solid-js/@solidjs/web ^2.0.0-rc.0, so the rename and the rc bump land together.

    @tanstack/router-plugin is intentionally untouched: it detects the Solid JSX plugin by its Vite plugin name (solid), which the renamed package still registers, and its vite-plugin-solid peer is optional — so it keeps working for both Solid 1 and Solid 2 consumers without a change.

    Also bumps @tanstack/solid-query and @tanstack/solid-query-devtools to ^6.0.0-rc.0 (whose peer requires solid-js >=2.0.0-rc.0), and converges @tanstack/query-core on 5.101.4solid-query depends on query-core 5.101.0, which previously resolved to a stale 5.99.0 and produced two incompatible QueryClient types.

  • Updated dependencies [56cc90e]:

    • @tanstack/solid-router@2.0.0-rc.0