How to stop loader from working when you modify a query using nuqs

[Lqm1]

I use nuqs to manage the state of my queries, but when I change the state, the loader runs.
I want to control behavior only on the client when state is changed using nuqs. I want loader to work only at the first load.
loader also handles queries.

export const Route = createFileRoute("/users/$id")({
	validateSearch: z.object({
		index: z.number().int().nonnegative().optional(),
		type: typeSchema.optional(),
	}),
	loaderDeps: ({ search: { index, type } }) => ({
		index,
		type,
	}),
	loader: async ({ params: { id }, deps: { index, type } }) => {
		// process...
	},

[schiller-manuel]

shouldReload might help. other than that, if you have something in loaderDeps, it will cause loader to run.

[travisbreaks]

The nuqs adapter calls router.navigate() under the hood, so every nuqs state update flows through TanStack Router's navigation system. Since your loaderDeps destructure index and type from search params, the router sees the deps change and re-runs the loader. That's working as designed.

If index and type are purely client-side UI state, the cleanest fix is to drop them from loaderDeps entirely. Keep them in validateSearch for type safety, read them via useSearch() in components, but let the loader only care about $id. The loader runs on initial load and when the path param changes; nuqs changes are invisible to it.

If the loader genuinely needs those params on first load but not on subsequent updates, shouldReload: false does what you want (as @schiller-manuel suggested). Loader fires on route entry, skips same-route navigations.