How to avoid overspecifying fields in queries in graphql while avoiding multiple network requests across pages

If I have two pages, StepsList and StepDetail, I understand it’s impossible to avoid overfetching on the first page (StepsList) if we want to avoid a second network request on StepDetail

// StepsList
steps {
  id
  name <- I have to specify this field here even if it's not used, to avoid a network request on StepsDetail, where this field is used
}

// StepDetail
steps {
  id
  name
}

However, is there a way using a JavaScript graphql client to avoid having to specify the redundant name field on StepsList, while still fetching it, and without using a shared fragment between StepsList and StepDetail? I’m trying to come up with a solution to reduce network requests while still keeping queries specified to the data used by the component they serve.

I don’t want to use a shared fragment because I’m finding them unwieldy in a larger project I’m working on.

// StepsList
steps {
  id
  # `name` is not specified
  # there is no shared fragment
  # but `name` is still fetched
}

// StepDetail
steps {
  id
  name
}