@trackunit/react-vite-test-setup 0.0.1

package/src/setupMatchMediaMock.d.ts

@@ -0,0 +1,23 @@
+/**
+ * Mocks the window.matchMedia API for testing environments.
+ *
+ * This function creates a mock implementation of the window.matchMedia method that
+ * is commonly used for responsive design and media queries. The mock always returns
+ * a MediaQueryList-like object with standard methods and properties, but with default
+ * values (matches set to false).
+ *
+ * This allows tests of components that use media queries to run without errors in
+ * Jest's JSDOM environment, which doesn't implement matchMedia natively.
+ *
+ * Ideal for testing:
+ * - Responsive components
+ * - Components that adapt to screen size changes
+ * - Components that use CSS media query matching in JavaScript
+ *
+ * @example
+ * // In your jest setup file
+ * import { setupMatchMediaMock } from '@trackunit/react-vite-test-setup';
+ *
+ * setupMatchMediaMock();
+ */
+export declare const setupMatchMediaMock: () => void;

package/src/setupReactTestingLibrary.d.ts

@@ -0,0 +1,44 @@
+import "@testing-library/jest-dom/vitest";
+/**
+ * Sets up React Testing Library and Okta authentication mocks for testing.
+ *
+ * Behaviour:
+ *  - The top-level `afterEach` further up this file (which clears mocks
+ *    and runs RTL `cleanup()`) is registered as a side effect of importing
+ *    this module - that's intentional and existed before this refactor.
+ *  - Calling `setupReactTestingLibrary()` additionally:
+ *      1. Registers the `@okta/okta-react` mock via `vi.doMock` so
+ *         `useOktaAuth()` returns a fixed authenticated session. Opt-in:
+ *         the mock is NOT hoisted, so tests that need the real okta
+ *         hook (or their own mock) are unaffected unless they explicitly
+ *         call this.
+ *      2. Installs the tanstack-router Response polyfill (keeps it
+ *         opt-in because it mutates `globalThis.Response`);
+ *      3. Calls `setupTranslations()` so the
+ *         `useTranslation`/`useNamespaceTranslation` hooks always
+ *         return a mocked i18next instance. Under Vitest, the
+ *         shared jest-preset's `setupFilesAfterEnv` is no longer
+ *         loaded, so projects that previously got translation
+ *         setup "for free" otherwise blow up at the first
+ *         `i18NextInstance.exists is not a function` call. Baking
+ *         it in here means projects can't forget it - the cost is
+ *         mocking i18n in tests that don't use it (harmless: the
+ *         mock only kicks in if the spec imports react-i18next).
+ *      4. Installs `setupMatchMediaMock()`, `setupResizeObserver()`
+ *         and `setupIntersectionObserver()`. Every component test
+ *         needs these three under jsdom, and missing any of them
+ *         causes React's render to throw, which `vitest-fail-on-console`
+ *         then re-raises as "Expected test not to call console.error()".
+ *         Under jest the workspace preset installed them via
+ *         `setupFilesAfterEnv`; under vitest only what each project's
+ *         setup file explicitly imports runs, so most setup files
+ *         called `setupReactTestingLibrary()` plus `setupFailOnConsole()`
+ *         but forgot the basic-DOM triplet. Folding the triplet in
+ *         here means "set up RTL" reads naturally as "set up
+ *         everything you need to render a component".
+ *
+ * @example
+ * import { setupReactTestingLibrary } from '@trackunit/react-vite-test-setup';
+ * setupReactTestingLibrary();
+ */
+export declare const setupReactTestingLibrary: () => void;

package/src/setupReactVirtualizedAutoSizer.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Mocks the `react-virtualized-auto-sizer` component for testing
+ * environments.
+ *
+ * Provides fixed dimensions (600x600) so tests don't need real DOM
+ * measurements. Especially useful for components using virtualized lists or
+ * grids.
+ *
+ * Opt-in: the mock is registered via `vi.doMock` so it is
+ * NOT hoisted and only takes effect once `setupReactVirtualizedAutoSizer()`
+ * is called from a test setup file. Tests that need the real component (or
+ * their own mock) are unaffected unless they explicitly call this.
+ *
+ * @example
+ * import { setupReactVirtualizedAutoSizer } from '@trackunit/react-vite-test-setup';
+ * setupReactVirtualizedAutoSizer();
+ */
+export declare const setupReactVirtualizedAutoSizer: () => void;

package/src/setupResizeObserver.d.ts

@@ -0,0 +1,19 @@
+/**
+ * Mock the ResizeObserver to be able to test components that use a resize
+ * observer (e.g. useMeasure, useContainerBreakpoints, and components that
+ * use them like BaseInput). Recommended for all React libs.
+ *
+ * Implementation note: under Vitest the mock was a single
+ * `vi.fn().mockImplementation(...)` so callers could:
+ *   1. `new global.ResizeObserver(cb)` from the SUT (the implementation
+ *      function is callable with `new` because it's a `function` expression
+ *      which has a working `[[Construct]]` slot), AND
+ *   2. `(global.ResizeObserver as Mock).mockImplementation(...)` from the
+ *      spec to capture the callback / inspect constructor arguments.
+ *
+ * Vitest 4's `vi.fn()` is also constructable when the impl is a `function`
+ * expression (arrow functions are *not* constructable), so we keep the
+ * same shape - this preserves both call sites that the migration would
+ * otherwise have to rewrite.
+ */
+export declare const setupResizeObserver: () => void;

package/src/setupTanstackReactRouter.d.ts

@@ -0,0 +1,18 @@
+/**
+ * Mocks the `@tanstack/react-router` library for testing environments.
+ *
+ * Replaces `useNavigate` with a no-op so components that call the
+ * navigation function during a test do not throw outside a router context.
+ *
+ * Opt-in: the mock is registered via `vi.doMock` so it is
+ * NOT hoisted and only takes effect once `setupTanstackReactRouter()` is
+ * called from a test setup file. Tests that need the real `useNavigate`
+ * (or their own mock) are unaffected unless they explicitly call this.
+ *
+ * @example
+ * // In your vitest setup file
+ * import { setupTanstackReactRouter } from '@trackunit/react-vite-test-setup';
+ *
+ * setupTanstackReactRouter();
+ */
+export declare const setupTanstackReactRouter: () => void;

package/src/setupTanstackReactVirtualize.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Mocks the `@tanstack/react-virtual` library for testing environments.
+ *
+ * Replaces `useVirtualizer` with a deterministic implementation that
+ * returns every item (no real DOM virtualisation), so tests can assert on
+ * the full rendered list without worrying about scroll-driven windowing.
+ *
+ * Opt-in: the mock is registered via `vi.doMock` so it is
+ * NOT hoisted and only takes effect once `setupTanstackReactVirtual()` is
+ * called from a test setup file. Tests that need the real virtualizer (or
+ * their own mock) are unaffected unless they explicitly call this.
+ *
+ * @example
+ * import { setupTanstackReactVirtual } from '@trackunit/react-vite-test-setup';
+ * setupTanstackReactVirtual();
+ */
+export declare const setupTanstackReactVirtual: () => void;

package/src/setupTimeAndLanguage.d.ts

@@ -0,0 +1,35 @@
+/**
+ * Mocks the Temporal API to use a fixed time zone for testing.
+ *
+ * This function specifically mocks the Temporal.Now.timeZoneId method from the
+ * Temporal library to always return "Europe/Copenhagen", ensuring consistent
+ * time zone-dependent behavior in tests regardless of where they run.
+ *
+ * Note: the host process timezone is also pinned to UTC at module load via
+ * `process.env.TZ` above, so non-Temporal Date arithmetic is deterministic.
+ *
+ * @example
+ * // In your vitest setup file
+ * import { setupTimeZone } from '@trackunit/react-vite-test-setup';
+ *
+ * setupTimeZone();
+ */
+export declare const setupTimeZone: () => void;
+/**
+ * Sets up time, animation, and language-related mocks for testing environments.
+ *
+ * This function configures multiple aspects of the testing environment:
+ * 1. Sets a fixed time zone using setupTimeZone()
+ * 2. Disables React Spring animations for faster, deterministic tests
+ * 3. Overrides setTimeout and setInterval to execute immediately (0ms delay)
+ *
+ * These changes make tests faster and more predictable by eliminating real-time
+ * delays, animations, and time zone dependencies that could cause flaky tests.
+ *
+ * @example
+ * // In your jest setup file
+ * import { setupTimeAndLanguage } from '@trackunit/react-vite-test-setup';
+ *
+ * setupTimeAndLanguage();
+ */
+export declare const setupTimeAndLanguage: () => void;

package/src/setupTranslations.d.ts

@@ -0,0 +1,17 @@
+/**
+ * Sets up internationalization and translation mocks for testing environments.
+ *
+ * Mock translations for react-i18next and @trackunit/i18n-library-translation. It creates
+ * simple mock implementations that return the key string as the translation, which allows
+ * for testing internationalized components without the complexity of actual translations.
+ *
+ * The mocks support common translation components and hooks like Trans, useTranslation,
+ * NamespaceTrans, and useNamespaceTranslation.
+ *
+ * @example
+ * // In your jest setup file
+ * import { setupTranslations } from '@trackunit/react-vite-test-setup';
+ *
+ * setupTranslations();
+ */
+export declare const setupTranslations: () => void;

package/src/setupWebStreams.d.ts

@@ -0,0 +1,16 @@
+/**
+ * Sets up Web Streams API polyfills for testing environments.
+ *
+ * Web Streams API polyfills from web-streams-polyfill. These polyfills provide implementations
+ * of modern streaming APIs that may not be available in the Jest/JSDOM testing environment.
+ *
+ * The setup enables testing of components and utilities that rely on the Web Streams API,
+ * such as those that process streaming data or implement custom stream transformations.
+ *
+ * @example
+ * // In your jest setup file
+ * import { setupWebStreams } from '@trackunit/react-vite-test-setup';
+ *
+ * setupWebStreams();
+ */
+export declare const setupWebStreams: () => void;