revalidateOnMutate: false configuration setting

[gkiely]

This would set revalidate: false for all bound mutations. Currently it is true by default. https://swr.vercel.app/docs/mutation.en-US#parameters

This would be useful when the api returns a result where revalidation is unnecessary or the developer knows the result of a successful response.

[manimovassagh]

Until this gets built in, you can achieve this today with a global onSuccess callback in SWRConfig:

<SWRConfig
  value={{
    revalidateOnMutate: false, // this option does not exist yet, but...
  }}
>

What you can do right now is wrap useSWRMutation in a custom hook that defaults revalidate: false:

import useSWRMutation from "swr/mutation";
import type { SWRMutationConfiguration } from "swr/mutation";

export function useMutation<T, E = any>(
  key: string,
  fetcher: (key: string, options: { arg: any }) => Promise<T>,
  options?: SWRMutationConfiguration<T, E> & { revalidate?: boolean }
) {
  return useSWRMutation(key, fetcher, {
    revalidate: false, // default to no revalidation
    ...options,        // allow overriding per-call
  });
}

Then use it everywhere instead of the raw hook:

const { trigger } = useMutation("/api/items", updateItem);
// No revalidation by default

const { trigger } = useMutation("/api/items", updateItem, { revalidate: true });
// Opt-in when you need it

This is especially useful when your API returns the updated resource and you use populateCache to update the local cache directly — revalidating on top of that is just a wasted request.

That said, having a first-class revalidateOnMutate config option in SWRConfig would be cleaner than every team building their own wrapper.