I don't know if provide/inject can solve your problem.

See vuejs/rfcs#477. Discussion is welcome.

Update: solved via vnode.props

After more investigation, filtering by !== undefined doesn't actually work. Vue applies boolean casting before the props object reaches userland — so by the time you check, outlined is already false, not undefined. false !== undefined is true, so all 28+ boolean props pass the filter anyway.

The correct fix is to check getCurrentInstance().vnode.props — it contains only the props explicitly passed by the parent, with no casting applied:

import { computed, getCurrentInstance, type ComputedRef } from 'vue'

const toKebabCase = (str: string) => str.replace(/([A-Z])/g, '-$1').toLowerCase()

export function useForwardProps<T extends Record<string, unknown>>(
  props: T
): ComputedRef<Partial<T>> {
  const instance = getCurrentInstance()

  return computed(() => {
    const vnodeProps = instance?.vnode.props ?? {}
    const result: Record<string, unknown> = {}

    for (const key in props) {
      if (key in vnodeProps || toKebabCase(key) in vnodeProps) {
        result[key] = props[key]
      }
    }

    return result as Partial<T>
  })
}

toKebabCase is needed because the template may use hide-bottom-space while defineProps declares it as hideBottomSpace — vnode.props stores keys in whichever form the parent wrote them.

Verified: with <MyWrapper label="test" /> (no booleans passed), forwarded now contains exactly 1 key (label), down from 29 with the !== undefined approach.

Question: forced cast with exactOptionalPropertyTypes

Since useForwardProps returns Partial<T>, I ran into a TypeScript error when binding to components that have required props (like Quasar's QTable, which requires rows).

With exactOptionalPropertyTypes: true enabled (Quasar sets this in its default tsconfig), spreading Partial<QTableProps> onto <q-table> fails — TS can't prove the required props are present. The only workaround I found is an explicit cast in the template:

<q-table v-bind="{ ...$attrs, ...(forwarded as QTableProps) }" />

Is there a cleaner way to handle this without the cast? Returning T instead of Partial<T> from useForwardProps breaks exactOptionalPropertyTypes on the other end. Feels like a dead end either way.