Releases: QwikDev/qwik
[email protected]
[email protected]
@builder.io/[email protected]
This patch release is all about Qwik City.
🐞 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 thiscontext restored in Qwik City handlers
thisinside 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.
@builder.io/[email protected]
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:3000and a user visited from127.0.0.1:3000, SPA routing would be broken.Internally, useNavigate's context provider
gotochecks 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. -
🐞🩹
thisin various Qwik-City handlers is nowRequestEventagain. (by @wmertens in #8111)