Files
stack/packages/mosaic/framework/skills/vueuse-functions/references/useVModels.md
T
fargo 1a822493ba format: apply repo prettier (3.8.1) to the folded skills tree
963 markdown files reformatted with the repository's pinned prettier so
pnpm format:check covers the folded tree like every other repo file.

The formatter's embedded-language pass also normalized code fences
(TS semicolons, closed HTML tags in examples, lowercased CSS hex colors,
one renumbered list that skipped an index). Alphanumeric token deltas vs
the fold commit were audited file-by-file; all are formatter-equivalent
markup normalizations plus the four sanitized skills.
2026-08-19 14:37:17 -05:00

1.3 KiB

category, related
category related
Component useVModel

useVModels

Shorthand for props v-model binding. Think it like toRefs(props) but changes will also trigger emit.

Usage

import { useVModels } from '@vueuse/core';

const props = defineProps({
  foo: string,
  bar: number,
});

const emit = defineEmits(['update:foo', 'update:bar']);

const { foo, bar } = useVModels(props, emit);

Options API

import { useVModels } from '@vueuse/core';

export default {
  props: {
    foo: String,
    bar: Number,
  },
  setup(props, { emit }) {
    const { foo, bar } = useVModels(props, emit);

    console.log(foo.value); // props.foo
    foo.value = 'foo'; // emit('update:foo', 'foo')
  },
};

Type Declarations

/**
 * Shorthand for props v-model binding. Think like `toRefs(props)` but changes will also emit out.
 *
 * @see https://vueuse.org/useVModels
 * @param props
 * @param emit
 * @param options
 *
 * @__NO_SIDE_EFFECTS__
 */
export declare function useVModels<P extends object, Name extends string>(
  props: P,
  emit?: (name: Name, ...args: any[]) => void,
  options?: UseVModelOptions<any, true>,
): ToRefs<P>;
export declare function useVModels<P extends object, Name extends string>(
  props: P,
  emit?: (name: Name, ...args: any[]) => void,
  options?: UseVModelOptions<any, false>,
): ToRefs<P>;