Merge pull request #1355 from MBombeck/dependabot/npm_and_yarn/development-weekly-d211ff7af0

build(deps-dev): bump the development-weekly group across 1 directory with 6 updates

package.json

@@ -121,15 +121,15 @@
     "@types/react": "^19.3.0",
     "@types/react-dom": "^19.3.0",
     "@types/web-push": "^3.6.4",
-    "@vitest/browser-playwright": "^5.0.5",
-    "@vitest/coverage-v8": "^5.0.5",
+    "@vitest/browser-playwright": "^5.1.0",
+    "@vitest/coverage-v8": "^5.1.0",
     "ajv": "^8.20.0",
     "eslint": "^9",
     "eslint-config-next": "16.4.5",
     "fast-check": "4.10.2",
     "knip": "^6.44.1",
     "lefthook": "^2.2.2",
-    "pdfjs-dist": "6.4.299",
+    "pdfjs-dist": "6.5.438",
     "prettier": "^3.9.10",
     "prettier-plugin-tailwindcss": "^0.8.1",
     "shadcn": "^4.23.0",
@@ -137,7 +137,7 @@
     "testcontainers": "^12.2.1",
     "tw-animate-css": "^1.4.0",
     "typescript": "^6",
-    "vitest": "^5.0.5",
+    "vitest": "^5.1.0",
     "vitest-browser-react": "^2.3.0"
   }
 }

tests/browser/clock.ts

@@ -6,9 +6,14 @@
  * is faked: timers, animation frames and the microtask queue keep running,
  * which is what Radix, TanStack Query and the URL-state queue wait on.
  * `setup.ts` restores the real clock after every test.
+ *
+ * `setSystemTime` without fake timers holds `Date` at the given instant.
+ * `useFakeTimers({ toFake: ["Date"] })` did the same until vitest 5.1, where
+ * the faked `Date` moves on with the wall clock and a form submitted a few
+ * hundred milliseconds in no longer sends the pinned instant.
  */
 import { vi } from "vitest";
 
 export function pinDate(iso: string): void {
-  vi.useFakeTimers({ toFake: ["Date"], now: new Date(iso) });
+  vi.setSystemTime(new Date(iso));
 }