Nuxt 4.4 Adds Custom Fetch Factories and Router v5
Nuxt 4.4 ships createUseFetch factories, Vue Router v5, and 28x faster dev route updates. Custom fetch instances with typed defaults cut API boilerplate, while the router upgrade drops unplugin-vue-router and clears the path for stable typed routes.
Why it matters
Nuxt 4.4 targets the three places Vue teams lose time: API boilerplate, dev server lag, and accessibility gaps. The new createUseFetch factory lets you bake baseURL, interceptors, and server flags into reusable composables that stay fully typed and SSR-compatible. That means less copy-paste in every page and fewer runtime misconfigurations when calling internal APIs. For teams running large codebases, the migration to unrouting cuts dev-server route recalculation by up to 28x when you edit existing pages, and makes route generation deterministic regardless of file ordering. If you ship ISR or SWR in serverless environments, the new payloadExtraction client mode stops the double-lambda cold-start problem where a cached route triggers an immediate second render.
What changed
Four concrete changes land in this release. First, createUseFetch and createUseAsyncData accept either a defaults object or a merge function, giving you full control over how per-call options combine with global config. Second, Vue Router v5 replaces the previous major version and removes the unplugin-vue-router dependency entirely; for most apps this is transparent, and it sets up typed routes to leave experimental status next. Third, definePageMeta now accepts a layout object with typed props, so layouts can receive per-page parameters like sidebar visibility or titles without provide/inject workarounds. Fourth, the new useAnnouncer composable and NuxtAnnouncer component expose polite and assertive ARIA live regions for dynamic content changes such as search results or form errors, supplementing the existing route announcer.
What to watch
Check whether you import unplugin-vue-router directly and remove it if so. Test createUseFetch against your current API composables to see if you can collapse multiple wrappers into one factory. If you use ISR or SWR with payload extraction, evaluate the new client mode to reduce serverless concurrency costs. The typed routes feature is still experimental but likely to stabilize soon given the router v5 foundation.
Interview question
What is the primary benefit of using createUseFetch over ad-hoc useFetch wrappers?
- a.It removes the need for unplugin-vue-router and makes route generation deterministic.
- b.It enables layouts to receive typed per-page parameters without provide/inject workarounds.
- c.It lets you bake baseURL, interceptors, and server flags into reusable, fully typed composables that remain SSR-compatible.Correct
- d.It reduces dev-server route recalculation time by up to 28x when editing existing pages.
Why? this is the answer
createUseFetch is designed to cut API boilerplate by embedding baseURL, interceptors, and server flags into reusable, fully typed composables that remain SSR-safe. Distractor B describes the Vue Router v5 upgrade's impact on dev-server performance, not fetch factories.
Just read this? Test yourself on what you have been reading.
Read the original → nuxt.com
You just looked this up. Could you explain it out loud?
That is the part interviews actually test. Tezvyn takes questions like this one and gives you what the interviewer is really checking, the answer that lands, and the mistake that ends the conversation, in the four minutes before your next meeting.
The iPhone app is on the way
We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.
Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.
We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.
See open roles