6 hours ago
tdesign-miniprogram

1.12.1

What's Changed

  • Navbar: 新增 placeholder 属性,默认值为 false;新增 zIndex 属性,默认值为 1 @anlyyao (#4116)
  • TabBar: 新增 placeholder 属性,默认值为 false;新增 zIndex 属性,默认值为 1 @anlyyao (#4116)
  • Badge: @anlyyao (#4137)
    • shape 属性新增 ribbon-right/ribbon-left/triangle-right/triangle-left 可选项,其中 ribbonribbon-right 等效
    • 优化 ribbon 实现,改用 background: linear-gradient(),移除伪元素相关样式
  • Popover: 新增 fixed API,适用于触发元素为 fixed 场景。⚠️ 当触发元素为 fixed 时,除了需要显示指定 fixed 属性为 true,还需在触发元素层添加 t-popover-wrapper--fixed 类,用于定位触发元素。@Wesley-0808 (#4114)
  • Search: @anlyyao (#4150)
    • 确保点击清空按钮后,组件内容清空但保持聚焦
    • 新增 cursor-color 属性

🐞 Bug Fixes

  • ChatContent: 修复角色为 system 时文本颜色错误 @anlyyao (#4112)
  • Toast: 修复 Toast 嵌套调用时 close 回调陷入循环的问题 @anlyyao (#4110)
  • Attachments: 修复删除按钮在华为 pure70 机型上显示不完整的问题 @waiterxiaoyy (#4124)
  • DateTimePicker: 修复插槽名重复导致的控制台告警 @anlyyao (#4126)
  • Picker:
    • 优化性能减少掉帧 @jarmywang @Boomkaa (#4120)
    • 修复平铺模式 value 变化未能准确监听 @jarmywang (#4120)
  • ColorPicker: 补充 styleIsolation 配置项,解决外部样式无法覆盖组件样式问题 @anlyyao (#4138)
  • SwipeCell: 消除 IntersectionObserver is using slowest path 警告 @anlyyao (#4139)
  • Tabs: 消除 IntersectionObserver is using slowest path 警告 @anlyyao (#4139)
  • Progress: @anlyyao (#4153)
    • 修复深色模式下环形进度条内部背景色错误
    • 修复环形进度条内部文本间距错误

New Contributors

Full Changelog: https://github.com/Tencent/tdesign-miniprogram/compare/1.12.0...1.12.1

6 hours ago
meta2d.js

v1.1.11

v1.1.11

8 hours ago
rspack

v1.7.0

🎉 See Announcing Rspack 1.7 for more details.

What's Changed

Performance Improvements ⚡

New Features 🎉

Bug Fixes 🐞

Refactor 🔨

Document Updates 📖

Other Changes

Full Changelog: https://github.com/web-infra-dev/rspack/compare/v1.6.8...v1.7.0

16 hours ago
next.js

v16.1.1-canary.10

Misc Changes

  • chore(turbo-tasks-malloc): replace mimalloc-rspack to mimalloc: #87815

Credits

Huge thanks to @xusd320 for helping!

16 hours ago
react-resizable

3.1.0

3.1.0 (Dec 30, 2025)

  • 🐛 Bugfix: Fix onResizeStop reporting stale size data due to React's batched state updates. The callback now uses the stored size from the last onResize call. #250
  • ➕ Feature: React 18 support.
  • ✏ Chore: Migrate test suite from Enzyme to React Testing Library. #249
  • ✏ Chore: Update react-draggable to ^4.5.0.
  • ✏ Chore: Update react-test-renderer to ^18.
16 hours ago
react-grid-layout

2.2.2

🧪 Tests

  • prevent infinite loop when dragging external items in controlled state (#2210) - #2225 by @STRML

🔧 Internal Changes

  • prevent infinite loop when dragging external items in controlled state (#2210) - #2225 by @STRML
17 hours ago
react-pdf

v10.3.0

What's new?

  • Added support for filterAnnotations prop in Page component (#1991).
  • Made the code more resilient to promise cancellations (#974).

What's changed?

  • Tests are no longer shipped to npm. This helped reducing publish size from 416 kB to 303 kB.
  • Updated Next.js samples.

Bug fixes

  • Fixed incorrectly calculated dimensions of rotated pages in Page onLoadSuccess handler (#2027). Thanks, @wkirby!
20 hours ago
tldraw

v4.2.2

Generated from commits between v4.2.2 and HEAD

21 hours ago
virtual

@tanstack/vue-virtual@3.13.14

Patch Changes

  • Updated dependencies [6d9274c]:
    • @tanstack/virtual-core@3.13.14
21 hours ago
virtual

@tanstack/virtual-core@3.13.14

Patch Changes

  • Fix: Correct lane assignments when lane count changes dynamically (#1095)

    Fixed a critical bug where changing the number of lanes dynamically would cause layout breakage with incorrect lane assignments. When the lane count changed (e.g., from 3 to 2 columns in a responsive masonry layout), some virtual items would retain their old lane numbers, causing out-of-bounds errors and broken layouts.

    Root Cause: After clearing measurements cache on lane change, the virtualizer was incorrectly restoring data from initialMeasurementsCache, which contained stale lane assignments from the previous lane count.

    Fix: Skip initialMeasurementsCache restoration during lane transitions by checking the lanesSettling flag. This ensures all measurements are recalculated with correct lane assignments for the new lane count.

    Before:

    // With lanes = 2
    virtualItems.forEach((item) => {
      columns[item.lane].push(item) // ❌ Error: item.lane could be 3
    })

    After:

    // With lanes = 2
    virtualItems.forEach((item) => {
      columns[item.lane].push(item) // ✅ item.lane is always 0 or 1
    })

    This fix is essential for responsive masonry layouts where column count changes based on viewport width. No performance impact as it only affects the lane change transition path.