Skip to content

Feature/vite 8 beta - #7

Draft
tuj wants to merge 22 commits into
release/3.0.0from
feature/vite-8-beta
Draft

Feature/vite 8 beta#7
tuj wants to merge 22 commits into
release/3.0.0from
feature/vite-8-beta

Conversation

@tuj

@tuj tuj commented Jun 2, 2026

Copy link
Copy Markdown

@tuj tuj self-assigned this Jun 2, 2026
tuj added 2 commits August 31, 2026 05:06
Resolved three conflicts:

- package.json: kept react-router/react-router-dom at ^7.12.0. The incoming
  side dropped the stale react-router ^5.2.0 dependency; this branch had
  already replaced it with the real v7 package, so that intent is preserved.
- CHANGELOG.md: kept both sides, with the Unreleased entry above the
  incoming rc4-rc8 history.
- package-lock.json: regenerated with npm rather than hand-merged.

Refreshed the dependency tree while resolving the lockfile: npm audit goes
from 12 advisories (8 high) to zero. All but one were fixed by in-range
updates; esbuild needed ^0.27.2 -> ^0.28.2.

Verified: vite build emits all three entries, vitest 57/57 pass.
fixTime built its pinned clock by mutating the current date. On the 31st of
a month, setMonth(8) carried day-of-month 31 into September, which has 30
days, so the date overflowed to 1 October and setDate(15) then landed on
15 October instead of 15 September. calendar-0-single-booking asserted on
"september" and failed.

Constructing the date in a single call keeps it stable on every calendar
date while still tracking the current year.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant