Version Packages (next)

Author: github-actions[bot]

.changeset/pre.json

@@ -105,6 +105,7 @@
     "cookbook-app-react-people_fix-doc-link",
     "cookbook-app-react-router_openapi-mock-fixture",
     "cookbook-app-react-router_rename-configure-fixture",
+    "cookbook-app-react-router_stop-reading-window-location",
     "cookbook-app-react_add-app-test",
     "dev-portal_migrate-browser-tests",
     "docs-restructure",
@@ -165,9 +166,12 @@
     "vitest-plugin-react-app_default-viewport",
     "vitest-plugin-react-app_define-project",
     "vitest-plugin-react-app_document-override",
+    "vitest-plugin-react-app_exclude-dts-warmup",
     "vitest-plugin-react-app_initial-release",
     "vitest-plugin-react-app_migration-guide",
+    "vitest-plugin-react-app_optional-feature-flag-mock",
     "vitest-plugin-react-app_rename-configure-fixtures",
+    "vitest-plugin-react-app_revert-memory-history",
     "vitest-plugin-react-app_why-browser-mode"
   ]
 }

cookbooks/app-react-router/CHANGELOG.md

@@ -1,5 +1,15 @@
 # Change Log
 
+## 5.0.4-next.2
+
+### Patch Changes
+
+- 1fdd87f: Tests no longer read or seed `window.location`/`window.history`. Now that
+  `resolveFusion` defaults navigation to in-memory history, real browser
+  location never reflects the app's navigation state — assertions read
+  `app.navigation.path.pathname` instead, and link `href` assertions match on
+  path rather than full origin.
+
 ## 5.0.4-next.1
 
 ### Patch Changes

cookbooks/app-react-router/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@equinor/fusion-framework-cookbook-app-react-router",
-  "version": "5.0.4-next.1",
+  "version": "5.0.4-next.2",
   "description": "",
   "private": true,
   "type": "module",

cookbooks/app-react-router/src/components/Navigation.test.tsx

@@ -24,32 +24,35 @@ testWithRouter('navigating to a page updates the URL', async ({ render, app }) =
   await unmount();
 });
 
-testWithRouter('the active link swaps when navigating to a different page', async ({ render, app }) => {
-  const { getByText, unmount } = await render(<Navigation />);
-
-  // active state is only reflected as a styled-components color, not a DOM attribute
-  const colorOf = (label: string) => getComputedStyle(getByText(label).element()).color;
-
-  // navigate via the router's own click handler first, so its internal location is
-  // guaranteed to be in sync rather than relying on the initial location above
-  await getByText('Home').click();
-  await vi.waitFor(() => expect(app.navigation.path.pathname).toBe('/'));
-
-  // Users is never navigated to in this test, so its color is a stable "inactive" reference
-  const inactiveColor = colorOf('Users');
-  await vi.waitFor(() => {
-    expect(colorOf('Home')).not.toBe(inactiveColor);
-    expect(colorOf('Products')).toBe(inactiveColor);
-  });
-
-  await getByText('Products').click();
-
-  // the URL changes synchronously on click, so styling lags at least one render behind it —
-  // retry on the color itself rather than on the pathname, which would resolve too early
-  await vi.waitFor(() => {
-    expect(colorOf('Home')).toBe(inactiveColor);
-    expect(colorOf('Products')).not.toBe(inactiveColor);
-  });
-
-  await unmount();
-});
+testWithRouter(
+  'the active link swaps when navigating to a different page',
+  async ({ render, app }) => {
+    const { getByText, unmount } = await render(<Navigation />);
+
+    // active state is only reflected as a styled-components color, not a DOM attribute
+    const colorOf = (label: string) => getComputedStyle(getByText(label).element()).color;
+
+    // navigate via the router's own click handler first, so its internal location is
+    // guaranteed to be in sync rather than relying on the initial location above
+    await getByText('Home').click();
+    await vi.waitFor(() => expect(app.navigation.path.pathname).toBe('/'));
+
+    // Users is never navigated to in this test, so its color is a stable "inactive" reference
+    const inactiveColor = colorOf('Users');
+    await vi.waitFor(() => {
+      expect(colorOf('Home')).not.toBe(inactiveColor);
+      expect(colorOf('Products')).toBe(inactiveColor);
+    });
+
+    await getByText('Products').click();
+
+    // the URL changes synchronously on click, so styling lags at least one render behind it —
+    // retry on the color itself rather than on the pathname, which would resolve too early
+    await vi.waitFor(() => {
+      expect(colorOf('Home')).toBe(inactiveColor);
+      expect(colorOf('Products')).not.toBe(inactiveColor);
+    });
+
+    await unmount();
+  },
+);

cookbooks/app-react-router/src/components/product/ProductCard.test.tsx

@@ -19,7 +19,9 @@ testWithRouter(
     await expect.element(getByText(/✓ in stock/i)).toBeInTheDocument();
 
     const link = getByRole('link', { name: /view details/i });
-    await expect.element(link).toHaveAttribute('href', expect.stringContaining(`/products/${baseProduct.id}`));
+    await expect
+      .element(link)
+      .toHaveAttribute('href', expect.stringContaining(`/products/${baseProduct.id}`));
 
     await unmount();
   },

packages/vitest-plugin/react-app/CHANGELOG.md

@@ -1,5 +1,27 @@
 # @equinor/fusion-framework-vitest-plugin-react-app
 
+## 1.0.0-next.5
+
+### Minor Changes
+
+- 1fdd87f: `resolveFusion` (and both the `/test` fixtures and `testApp`) now enable the feature-flag
+  mock by default, with no flags enabled, so `useFeature` needs no `localStorage` or URL
+  seeding in tests.
+
+  `@equinor/fusion-framework-module-feature-flag` is an optional peer dependency: the mock is
+  only wired up when the package is actually installed, so apps that don't use feature flags
+  aren't forced to add it. Install it to get the default mock; call `enableFeatureFlagMock`
+  again inside `configureFusion` to seed specific flags.
+
+### Patch Changes
+
+- 1fdd87f: Exclude `.d.ts` files from the default `server.warmup.clientFiles` and `optimizeDeps.entries`
+  globs in `defineProject`. Previously, an app shipping a CJS-style declaration file (for example
+  one using `export =`) failed the Vite warmup scan, since it was loaded as ESM.
+- 1fdd87f: Revert the mocked framework's default navigation history from browser history back to in-memory
+  history. Browser history leaked URL/history state between tests; `configureFusion`/`enableNavigation`
+  can still opt back into browser history for a test that specifically needs it.
+
 ## 1.0.0-next.4
 
 ### Major Changes

packages/vitest-plugin/react-app/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@equinor/fusion-framework-vitest-plugin-react-app",
-  "version": "1.0.0-next.4",
+  "version": "1.0.0-next.5",
   "description": "Vite plugin resolving an application's manifest, config, and module-configurator as virtual modules for testing.",
   "type": "module",
   "exports": {