The latest news releases from the Qwik team

This patch release is all about Qwik City.

:lady_beetle: Fixes:

• SPA routing works regardless of origin mismatch Fixed #8093: SPA navigation was broken when the visited origin (e.g., 127.0.0.1:3000) differed from the SSG/Vite config origin (e.g., localhost:3000). useNavigate's internal origin check now uses the browser's actual href for the initial route, preventing false full-page reloads. by @termermc in #8097
• this context restored in Qwik City handlers this inside route loaders, actions, and other handlers is once again the correct RequestEvent object. by @wmertens in #8111

These are subtle but important fixes and we recommend upgrading ASAP.

Patch Changes

• 🐞🩹 history behavior in some edge cases has been brought inline with the E2E tests that were accidentally disabled. (the tests can't be disabled any more either) (by @wmertens in 206f3e0)

• 🐞🩹 SPA routing is broken unless origin matches value in in vite.config #8093 (by @termermc in #8097)

  If the SSG origin was set to localhost:3000 and a user visited from 127.0.0.1:3000, SPA routing would be broken.

  Internally, useNavigate's context provider goto checks the new destination with the last route location. If the origin is different, it just does a normal browser navigation. This makes sense; links to other origins cannot use SPA routing. However, the initial route it compares was using an origin that came from the server environment.

  Now, the first navigation will set that initial route to the browser's actual href, eliminating the erroneous origin mismatch for SPA navigations.

• 🐞🩹 this in various Qwik-City handlers is now RequestEvent again. (by @wmertens in #8111)