[Vue warn]: Property or method is not defined on the instance but referenced during render

Javascriptvue.jsVuejs2Vue Component

Javascript Problem Overview


var MainTable = Vue.extend({
  template: "<ul>" +
    "<li v-for='(set,index) in settings'>" +
    "{{index}}) " +
    "{{set.title}}" +
    "<button @click='changeSetting(index)'> Info </button>" +
    "</li>" +
    "</ul>",
  data: function() {
    return data;
  }
});

Vue.component("main-table", MainTable);

data.settingsSelected = {};
var app = new Vue({
  el: "#settings",
  data: data,
  methods: {
    changeSetting: function(index) {
      data.settingsSelected = data.settings[index];
    }
  }
});

With the above code, the error below occurs when the button is clicked.

> [Vue warn]: Property or method "changeSetting" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option. (found in <MainTable>)

Javascript Solutions


Solution 1 - Javascript

Problem

> [Vue warn]: Property or method "changeSetting" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option. (found in <MainTable>)

The error is occurring because the changeSetting method is being referenced in the MainTable component here:

    "<button @click='changeSetting(index)'> Info </button>" +

However the changeSetting method is not defined in the MainTable component. It is being defined in the root component here:

var app = new Vue({
  el: "#settings",
  data: data,
  methods: {
    changeSetting: function(index) {
      data.settingsSelected = data.settings[index];
    }
  }
});

What needs to be remembered is that properties and methods can only be referenced in the scope where they are defined.

> Everything in the parent template is compiled in parent scope; everything in the child template is compiled in child scope.

You can read more about component compilation scope in Vue's documentation.

What can I do about it?

So far there has been a lot of talk about defining things in the correct scope so the fix is just to move the changeSetting definition into the MainTable component?

It seems that simple but here's what I recommend.

You'd probably want your MainTable component to be a dumb/presentational component. (Here is something to read if you don't know what it is but a tl;dr is that the component is just responsible for rendering something – no logic). The smart/container element is responsible for the logic – in the example given in your question the root component would be the smart/container component. With this architecture you can use Vue's parent-child communication methods for the components to interact. You pass down the data for MainTable via props and emit user actions from MainTable to its parent via events. It might look something like this:

Vue.component('main-table', {
  template: "<ul>" +
    "<li v-for='(set, index) in settings'>" +
    "{{index}}) " +
    "{{set.title}}" +
    "<button @click='changeSetting(index)'> Info </button>" +
    "</li>" +
    "</ul>",
  props: ['settings'],
  methods: {
    changeSetting(value) {
      this.$emit('change', value);
    },
  },
});


var app = new Vue({
  el: '#settings',
  template: '<main-table :settings="data.settings" @change="changeSetting"></main-table>',
  data: data,
  methods: {
    changeSetting(value) {
      // Handle changeSetting
    },
  },
}),

The above should be enough to give you a good idea of what to do and kickstart resolving your issue.

Solution 2 - Javascript

Should anybody land with the same silly problem I had, make sure your component has the 'data' property spelled correctly. (eg. data, and not date)

<template>
    <span>{{name}}</span>
</template>

<script>
export default {
  name: "MyComponent",
  data() {
    return {
      name: ""
    };
  }
</script>

Solution 3 - Javascript

In my case the reason was, I only forgot the closing

</script>

tag.

But that caused the same error message.

Solution 4 - Javascript

It's probably caused by spelling error

I got a typo at script closing tag

</sscript>

Solution 5 - Javascript

If you're experiencing this problem, check to make sure you don't have

methods: {
...
}

or

computed: {
...
}

declared twice

Solution 6 - Javascript

Remember to return the property

Another reason of seeing the Property "search" was accessed during render but is not defined on instance is when you forget to return the variable in the setup(){} function

So remember to add the return statement at the end:

export default {

  setup(){

    const search = ref('')
    //Whatever code

    return {search}

  }
}

Note: I'm using the Composition API

Solution 7 - Javascript

Adding my bit as well, should anybody struggle like me, notice that methods is a case-sensitive word:

<template>
    <span>{{name}}</span>
</template>

<script>
export default {
  name: "MyComponent",
  Methods: {
      name() {return '';}
  }
</script>

'Methods' should be 'methods'

Solution 8 - Javascript

I got this error when I tried assigning a component property to a state property during instantiation

export default {
 props: ['value1'],
 data() {
  return {
   value2: this.value1 // throws the error
   }
  }, 
 created(){
  this.value2 = this.value1 // safe
 }
}

Solution 9 - Javascript

If you use two times vue instance. Then it will give you this error. For example in app.js and your own script tag in view file. Just use one time

 const app = new Vue({
    el: '#app',
});

Solution 10 - Javascript

My issue was I was placing the methods inside my data object. just format it like this and it'll work nicely.

<script>
module.exports = {
	data: () => {
		return {
			name: ""
		}
	},
	methods: {
		myFunc() {
			// code
		}
	}
}
</script>

Solution 11 - Javascript

In my case, I wrote it as "method" instead of "methods". So stupid. Wasted around 1 hour.

Solution 12 - Javascript

It is most likely a spelling error of reserved vuejs variables. I got here because I misspelled computed: and vuejs would not recognize my computed property variables. So if you have an error like this, check your spelling first!

Solution 13 - Javascript

I had two methods: in the <script>, goes to show, that you can spend hours looking for something that was such a simple mistake.

Solution 14 - Javascript

In my case it was a property that gave me the error, the correct writing and still gave me the error in the console. I searched so much and nothing worked for me, until I gave him Ctrl + F5 and Voilá! error was removed. :'v

Solution 15 - Javascript

Although some answers here maybe great, none helped my case (which is very similar to OP's error message).

This error needed fixing because even though my components rendered with their data (pulled from API), when deployed to firebase hosting, it did not render some of my components (the components that rely on data).

To fix it (and given you followed the suggestions in the accepted answer), in the Parent component (the ones pulling data and passing to child component), I did:

// pulled data in this life cycle hook, saving it to my store
created() {
  FetchData.getProfile()
    .then(myProfile => {
      const mp = myProfile.data;
      console.log(mp)
      this.$store.dispatch('dispatchMyProfile', mp)
      this.propsToPass = mp;
    })
    .catch(error => {
      console.log('There was an error:', error.response)
    })
}
// called my store here
computed: {
    menu() {
        return this.$store.state['myProfile'].profile
    }
},

// then in my template, I pass this "menu" method in child component
 <LeftPanel :data="menu" />

This cleared that error away. I deployed it again to firebase hosting, and viola!

Hope this bit helps you.

Solution 16 - Javascript

Look twice the warning : Property _____ was accessed during render but is not defined on instance. So you have to define it ... in the data function for example which commonly instantiate variables in a Vuejs app. and, it was my case and that way the problem has been fixed. That's all folk's !

Solution 17 - Javascript

In my case, I forgot to add the return keyword:

computed: {
    image(){
        this.productVariants[this.selectedVariant].image;
    },
    inStock(){
       this.productVariants[this.selectedVariant].quantity;
    }
}

Change to:

computed: {
    image(){
        return this.productVariants[this.selectedVariant].image;
    },
    inStock(){
       return this.productVariants[this.selectedVariant].quantity;
    }
}

Solution 18 - Javascript

if you have any props or imported variables (from external .js file) make sure to set them properly using created like this;

make sure to init those vars:

import { var1, var2} from './constants'

//or

export default {
     data(){
      return {
       var1: 0,
       var2: 0,
       var3: 0,
      },
    },
    props: ['var3'],
    created(){
     this.var1 = var1;
     this.var2 = var2;
     this.var3 = var3;
     }
    

Solution 19 - Javascript

In my case due to router name not in string:

:to="{name: route-name, params: {id:data.id}}"

change to router name in string:

:to="{name: 'router-name', params: {id:data.id}}"

Solution 20 - Javascript

In my case I was trying to pass a hard coded text value to another component with:

 ChildComponent(:displayMode="formMode")

when it should be:

ChildComponent(:displayMode="'formMode'")

note the single quotes to indicate text instead of calling a local var inside the component.

Solution 21 - Javascript

Some common cases of this error

  • Make sure your component has the data property spelled correctly
  • Make sure your template is bot defined within another component’s template.
  • Make sure you defined the variable inside data object
  • Make sure your router name in string

Get some more sollution

Solution 22 - Javascript

If you're using the Vue3 <script setup> style, make sure you've actually specified setup in the opening script tag:

<script setup>

I had lapsed into old habits and only created a block with <script>, but it took a while to notice it.

https://v3.vuejs.org/api/sfc-script-setup.html

Solution 23 - Javascript

mine was to re create the component and the error was gone. good thing i was just on the first part. weird. edit: i was using composition api

Solution 24 - Javascript

For me, I just forget to close script tag :-)

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionLorenzo D&#39;IsidoroView Question on Stackoverflow
Solution 1 - JavascriptWingView Answer on Stackoverflow
Solution 2 - Javascripttno2007View Answer on Stackoverflow
Solution 3 - Javascriptfrankfurt-laravelView Answer on Stackoverflow
Solution 4 - JavascriptbibsView Answer on Stackoverflow
Solution 5 - JavascriptChuks Jr.View Answer on Stackoverflow
Solution 6 - Javascriptluigi7upView Answer on Stackoverflow
Solution 7 - JavascriptDaniel KatzView Answer on Stackoverflow
Solution 8 - JavascriptI Want AnswersView Answer on Stackoverflow
Solution 9 - JavascriptHamza KhanView Answer on Stackoverflow
Solution 10 - JavascriptPwntasticView Answer on Stackoverflow
Solution 11 - JavascriptBalasubramanian SView Answer on Stackoverflow
Solution 12 - JavascriptmahatmanichView Answer on Stackoverflow
Solution 13 - Javascriptlearncodes123View Answer on Stackoverflow
Solution 14 - JavascriptJennifer Miranda BeusesView Answer on Stackoverflow
Solution 15 - JavascriptGelView Answer on Stackoverflow
Solution 16 - JavascriptmarcdahanView Answer on Stackoverflow
Solution 17 - JavascriptkodeKhalifaView Answer on Stackoverflow
Solution 18 - JavascriptLepyView Answer on Stackoverflow
Solution 19 - Javascriptfahd shaykhView Answer on Stackoverflow
Solution 20 - JavascriptaarkerioView Answer on Stackoverflow
Solution 21 - JavascriptMD SHAYONView Answer on Stackoverflow
Solution 22 - JavascriptCharles BrandtView Answer on Stackoverflow
Solution 23 - JavascriptricoView Answer on Stackoverflow
Solution 24 - JavascriptpmvpView Answer on Stackoverflow