Defined in: [providers.ts:14](https://github.com/TanStack/query/blob/main/packages/angular-query-experimental/src/providers.ts#L14)

for the entire application. Internally it calls `provideQueryClient`.

You can use `provideQueryClient` to provide a different `QueryClient` instance for a part

In this approach, you explicitly declare for each _route_ what data is going to be needed for that component tree, ahead of time. Because Server Rendering has traditionally needed all data to be loaded before rendering starts, this has been the dominating approach for SSR'd apps for a long time. This is still a common approach and you can read more about it in the [Server Rendering & Hydration guide](./ssr.md).

When integrating at the router level, you can choose to either _block_ rendering of that route until all data is present, or you can start a prefetch but not await the result. That way, you can start rendering the route as soon as possible. You can also mix these two approaches and await some critical data, but start rendering before all the secondary data has finished loading. In this example, we'll configure an `/article` route to not render until the article data has finished loading, as well as start prefetching comments as soon as possible, but not block rendering the route if comments haven't finished loading yet.

'useQuery[(]': 'useQuery(() => ',

'useQueries[(]': 'useQueries(() => ',

'useInfiniteQuery[(]': 'useInfiniteQuery(() => ',

}

if (relativeLinks.length > 0) {

relativeLinks.forEach((link) => {

relativeLinkExists(link, file)

})

}