Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Property "tag" was accessed during render but is not defined on instance

See original GitHub issue

I just installed lastest vue-kinesis version 2.0.4 and tried to use it in my Vue 3 project as follows:

yarn add vue-kinesis@next

import { createApp } from 'vue';
import VueKinesis from 'vue-kinesis';
import App from './App.vue';

createApp(App)
  .use(VueKinesis)
  .mount('#app');

<kinesis-container>
  <kinesis-element :strength="10">
    <Project />
  </kinesis-element>
</kinesis-container>

Where Project is one of my vue components, which is not displayed and i get the following warnings in the console:

runtime-core.esm-bundler.js:38 [Vue warn]: Property "tag" was accessed during render but is not defined on instance. 
  at <KinesisContainer> 
  at <MainContent> 
  at <App>

runtime-core.esm-bundler.js:38 [Vue warn]: Property "style" was accessed during render but is not defined on instance. 
  at <KinesisContainer> 
  at <MainContent> 
  at <App>

Issue Analytics

State:
Created 2 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

Aminermancommented, May 14, 2021

What if you set it to true?

That’s something I’m not aware of. If I understand well, you’re dropping the options API, but kinesis uses it. But I don’t know what to do in this case. Should I change all the code so it works with the composition API? It will take some time. I mean, it would mean that all the plugins should be migrated to the composition API just to take into account this use case? I don’t know what to think about this.

Let me know if setting it to true changes anything?

0reactions

Aminermancommented, May 14, 2021

Perfect 😃 That’s a good news.