Changelog - 米舟开源

Java Golang JavaScript Swift Android Rust Middleware

1 hours ago

starlight

withastro

@astrojs/starlight@0.41.6

Patch Changes

#4102 f1dddc0 Thanks @delucis! - Adds 1 new icon: forgejo

4 hours ago

quasar

quasarframework

Fixes

fix(position-engine): #16167 QMenu/QTooltip never appear in Firefox when their content uses flexbox (#18468)
fix(EventBus): support reserved event names (#18479)
fix(date): escape custom locale names (#18481)
fix(runSequentialPromises): normalize invalid concurrency (#18480)
fix(QDialog): #13395 keep focus inside a child moved out by fullscreen (#18474)
fix(QTable): #10445 separator borders leak into tables rendered in slots (#18495)
fix(QMenu,QDialog): #15598 #17081 closing an overlay scrolls a virtual-scroll list by one header height (#18473)
fix(ui): don't scroll when moving focus to blur/refocus targets
fix(QInfiniteScroll): reverse mode scrolls by a whole batch on load when CSS scroll anchoring is active #17848 #18476
fix(date): extractDate() now returns an Invalid Date instead of a misleading valid-looking date when the input cannot be parsed (#18478)
fix(QInput): defer masking during IME composition (#16618, #16629) (#18424)
fix(QCarousel): negative autoplay does not respect the panel direction
fix(QCheckbox;QToggle;QRadio): only inject the native input when it can be submitted
fix(QPagination): glossy prop not being used correctly
fix(QVirtualScroll): don't crash after the missing-slot error
fix(preventDraggable): make the already-applied guard effective

Behavior change: date.extractDate() and invalid input

Previously, extractDate() always constructed a valid Date, even when the input didn't match the mask or contained impossible values. Failures were silently normalized -- extractDate('not a date', 'YYYY-MM-DD') returned Jan 1 1900, 2024-02-30 rolled over to Mar 1, and out-of-range time components wrapped around (24:00 became 00:00, 13:60 became 13:00).

Now these inputs return an Invalid Date object. The function signature and return type are unchanged, but code that never checked validity will propagate NaN-based dates instead of wrong-but-valid ones. Check results with:

const parsed = date.extractDate(input, 'YYYY-MM-DD')
if (date.isValid(parsed)) { /* safe to use */ }
// or: Number.isNaN(parsed.getTime())

Valid input prefixes still parse — extra text after the masked portion is ignored, so extractDate('2024-02-29T13:05:06Z', 'YYYY-MM-DD') still works.

QDate and QTime are also stricter about model values with out-of-range time components (e.g. 24:00 with an HH:mm mask). QTime now shows its empty --:-- state instead of a silently wrapped time, and QDate (with a time-bearing custom mask only) treats such values as unparseable -- no day appears selected and the calendar opens at the default view. Valid model values are unaffected.

Donations

Quasar Framework is an open-source MIT-licensed project made possible due to the generous contributions by sponsors and backers. If Quasar is useful in your workflow and you want to support ongoing maintenance, please consider the following:

4 hours ago

react-three-fiber

pmndrs

v9.7.0

The headline updates for this release are the reconciler fixes. We did a pass to harden what is there against react-dom as the standard.

R3F's internal children were not being reordered correctly. Basically, if React reordered children, our internal map would drift out of sync and this would cause subtle bugs. This is now fixed. Thanks to @kvvasuu who reported it and @wanxiankai who offered a solution.
Pierced props now reset properly. We had a bug where if a pierce prop was unset, the reconciler would try to reset it to a default value. However, it would set it to the base object instead of the pierced prop. This is fixed now.

// Initial render
<mesh position-x={5} />

// Later render: prop removed
<mesh />

// bug: would set it to the base object
mesh.x = 0 // !!!

Host props now update properly. Host props are ones that we supply such as dispose and onUpdate. These now update properly. This also caused a subtle bug where imperatively updated values could get overwritten unexpectedly after unsetting the value in React. This is all fixed. Note: attach is fixed on first set and ignored if you try to dynamically update it.
Properly batch instance reconstruction. This one is pretty technical and if you are curious check out the test in the attached PR. Basically, there was an edge case where if two instances needed to reconstruct (because the args updated), one could be ignore if the other bailed out of updates because of a React.memo or similar. It is likely a problem you never had, but your agent would curse if you did.
Event priorities match react-dom. React allows for prioritizing events, for example continuous events like wheel get a higher priority over impulse events like pointer. We copy from the best here and use the same list react-dom does.
Support reconciler microtasks. The React reconciler has a cool feature where it can queue microtasks to defer work based on the priorities we set earlier.

What's Changed

chore: move eslint rules from parserOptions to top-level rules (#3706) by @in-ch in https://github.com/pmndrs/react-three-fiber/pull/3707
docs: update useFrame hook description to specify that the clock delta is in seconds by @AJamesPhillips in https://github.com/pmndrs/react-three-fiber/pull/3742
chore(CI): update test workflow actions to remove Node 20 deprecation warning by @Shushovan015 in https://github.com/pmndrs/react-three-fiber/pull/3710
docs: fix FBXLoader naming in loading-models by @pavan-sh in https://github.com/pmndrs/react-three-fiber/pull/3745
chore(docs): pmndrs/examples by @abernier in https://github.com/pmndrs/react-three-fiber/pull/3639
fix: act import by @krispya in https://github.com/pmndrs/react-three-fiber/pull/3807
fix: internal instance children synchronization after keyed reorder by @krispya in https://github.com/pmndrs/react-three-fiber/pull/3808
chore: remove CodeSandbox CI by @krispya in https://github.com/pmndrs/react-three-fiber/pull/3809
fix: Pierced prop reset by @krispya in https://github.com/pmndrs/react-three-fiber/pull/3810
fix: Internal instance props sync by @krispya in https://github.com/pmndrs/react-three-fiber/pull/3811
fix: Batch instance reconstruction hardening by @krispya in https://github.com/pmndrs/react-three-fiber/pull/3812
feat: Match react-dom event priorities by @krispya in https://github.com/pmndrs/react-three-fiber/pull/3815
feat: Support reconciler microtasks by @krispya in https://github.com/pmndrs/react-three-fiber/pull/3816

New Contributors

@in-ch made their first contribution in https://github.com/pmndrs/react-three-fiber/pull/3707
@AJamesPhillips made their first contribution in https://github.com/pmndrs/react-three-fiber/pull/3742
@Shushovan015 made their first contribution in https://github.com/pmndrs/react-three-fiber/pull/3710
@pavan-sh made their first contribution in https://github.com/pmndrs/react-three-fiber/pull/3745

Full Changelog: https://github.com/pmndrs/react-three-fiber/compare/v9.6.1...v9.7.0

7 hours ago

shadcn-ui

shadcn@4.16.1

Patch Changes

#11322 bfa1b5e9a69a155b2f590523d50fda810bde1a9a Thanks @AndrewBarba! - fix shadcn build failing with ENOENT when registry item names contain path segments (e.g. extension/foo) by creating nested output directories before writing
#11352 5ca53ca7c7dea390e0e78091ff7c54adc48c773a Thanks @shadcn! - forward search params to registries for server-side dynamic search