DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • TDD Typescript NestJS API Layers with Jest Part 1: Controller Unit Test
  • The Bill You Didn't See Coming
  • Securing AI/ML Workloads in the Cloud: Integrating DevSecOps with MLOps
  • MCP Servers Are Everywhere, but Most Are Collecting Dust: Key Lessons We Learned to Avoid That

Trending

  • LLM-Powered Deep Parsing for Industrial Inventory Search
  • Zero-Downtime Deployments for Java Apps on Kubernetes
  • Stop Debugging Glue Jobs Manually: Building an Agentic Observability Layer for Data Pipelines
  • No More Cheap Claude: 4 First Principles of Token Economics in 2026
  1. DZone
  2. Coding
  3. Languages
  4. How to Give Props Default Values in Vue

How to Give Props Default Values in Vue

Props are ubiquitous in Vue, so let's look at how to give them default values.

By 
Johnny Simpson user avatar
Johnny Simpson
·
May. 18, 22 · Tutorial
Likes (2)
Comment
Save
Tweet
Share
7.6K Views

Join the DZone community and get the full member experience.

Join For Free

When we use components in Vue, we often use properties or props to pass custom pieces of data down to the child component. For example, we can tell our child component that for this version of the component, "name" is set to "my-component":

Vue.js Component
 
<Component name="my-component" />

If we try to call this component without a name prop, it returns undefined in the code, or just as no text when rendered in HTML. Let's say our Component looks like this:

Vue.js Component
 
<script>
export default {
    props: {
        name: String
    },
    mounted() {
        console.log(this.name);
    }
}
</script>

<template>
    <p>
        Hi {{ name }}
    </p>
</template>

All our component does is defines a prop called name of type String, and console logs this property. It also displays it in the form Hi {{ name }}. The only issue here is that name is undefined when the component is called, no default name is given.

Setting Default Prop Values in Vue

Setting defaults prop values in Vue is easy. If you are using the Options API, then it's as easy as extending our property into an object. For example, if we want our name to have a default value of "there", then we update our prop to look like this:

Vue.js Component
 
export default {
    props: {
        name: {
            type: String,
            default: "there"
        }
    },
    mounted() {
        console.log(this.name);
    }
}

Now if no name is given, the message will simply say 'Hi there'

Setting Default Prop Values in Composition API

In the composition API, defining props uses the defineProps function. This function follows the same syntax as props defined on the Options API. Defining a prop without a default looks like this:

Vue.js Component
 
import { defineProps } from 'vue';

const props = defineProps({
    name: String
});

And then to add a default value, we extend name to have a default property, just as before:

Vue.js Component
 
import { defineProps } from 'vue';

const props = defineProps({
    name: {
        type: String,
        default: "there"
    }
});

Setting a Prop as Required in Vue

To avoid the need for setting a default value on a property, we can force a property to be required by using the required field. For example, if we want our name property to be defined, we'd simply set required to true:

Vue.js Component
 
<script setup>
import { defineProps } from 'vue';

const props = defineProps({
    name: {
        type: String,
        required: true
    }
});
</script>
API HTML IT Console (video game CLI) Data (computing) Object (computer science) Pass (software) Property (programming) Syntax (programming languages)

Published at DZone with permission of Johnny Simpson. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • TDD Typescript NestJS API Layers with Jest Part 1: Controller Unit Test
  • The Bill You Didn't See Coming
  • Securing AI/ML Workloads in the Cloud: Integrating DevSecOps with MLOps
  • MCP Servers Are Everywhere, but Most Are Collecting Dust: Key Lessons We Learned to Avoid That

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook