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

  • The Bill You Didn't See Coming
  • Securing AI/ML Workloads in the Cloud: Integrating DevSecOps with MLOps
  • Top 5 Payment Gateway APIs for Indian SaaS: A Developer’s Analysis
  • MCP Servers Are Everywhere, but Most Are Collecting Dust: Key Lessons We Learned to Avoid That

Trending

  • Chat with Your Oracle Database: SQLcl MCP + GitHub Copilot
  • Architecting Sub-Microsecond HFT Systems With C++ and Zero-Copy IPC
  • Java in a Container: Efficient Development and Deployment With Docker
  • The Vector Database Lie
  1. DZone
  2. Software Design and Architecture
  3. Integration
  4. The Difference between Created and Mounted in Vue

The Difference between Created and Mounted in Vue

Mounted and Created sound similar - but they do different things. Let's investigate.

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

Join the DZone community and get the full member experience.

Join For Free

In a previous article, I covered all the different lifecycle hooks in Vue. One of the things that most people get confused about when talking about lifecycle hooks, is the difference between created and mounted. They both have similar names, and they feel like they should do the same thing, but there are some subtle differences.

The Difference between Created and Mounted in Vue

To begin with, both created() and mounted() have access to the data and props on your prototype. For example, both hooks will console log 'My Message' below, as well as the default value for myProp, which is 'Some Prop':

Vue.js Component
 
export default {
    data() {
        return {
            msg: 'My Message'
        }
    },
    props: {
        myProp: {
            type: String,
            default: 'My Prop'
        }
    },
    created() {
        console.log(this.msg);
        console.log(this.myProp);
    },
    mounted() {
        console.log(this.msg);        
        console.log(this.myProp);
    }
}

Prop Inheritance for Created and Mounted

Note: even if you set a property, it will still be available both in created() and mounted()

The fundamental difference between created() and mounted() is that you do not have access to the DOM in created() yet. In our example, if we try to reference this.$el, it will return null in created(), and it will return the DOM element in mounted():

Vue.js Component
 
export default {
    created() {
        // Returns null
        console.log(this.$el);
    },
    mounted() {
        // Returns the DOM element in console:
        console.log(this.$el);     
    }
}

As such, any DOM manipulation, or even getting the DOM structure using methods like querySelector will not be available in created(). As mentioned in the article on lifecycle hooks, created() is great for calling APIs, while mounted() is great for doing anything after the DOM elements have completely loaded.

Composition API and Created or Mounted

The one caveat to this is that if you are using the Composition API, created(), and indeed beforeCreated() no longer exists. You have to instead use setup(). This function takes the place of both created() and beforeCreated(). Therefore, the DOM is still not available in setup(). The Composition API mounted() remains unchanged.

API Hook Prototype Console (video game CLI) Data (computing) Element Inheritance (object-oriented programming) Property (programming)

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

Opinions expressed by DZone contributors are their own.

Related

  • The Bill You Didn't See Coming
  • Securing AI/ML Workloads in the Cloud: Integrating DevSecOps with MLOps
  • Top 5 Payment Gateway APIs for Indian SaaS: A Developer’s Analysis
  • 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