Skip to content
This repository has been archived by the owner on Oct 31, 2021. It is now read-only.

It works but I get a warning [Vue warn]: Property "$createElement" was accessed during render but is not defined on instance. #2

Open
jimmybsilva opened this issue Apr 28, 2021 · 14 comments

Comments

@jimmybsilva
Copy link

[Vue warn]: Property "$createElement" was accessed during render but is not defined on instance.

it seems to be working good I was just wondering if there is a way to fix that warning?

Thanks in advance.

@gautam-patadiya
Copy link

I'm same error!

@bosquig
Copy link

bosquig commented Jun 7, 2021

Same error. I think it's related to the use of JSX. Could you fix it @jimmybsilva @gautam-patadiya @megafetis ?

@gautam-patadiya
Copy link

@bosquig no buddy I didn't

@xgblack
Copy link

xgblack commented Jul 3, 2021

I have also encountered the same problem, whether there is a solution?

@aehyok
Copy link

aehyok commented Jul 8, 2021

I'm same error!

@dreamxyz95
Copy link

Is there a fix for this?

@zhangyuan0532
Copy link

[Vue warn] too much! I hava 5961 messages in console.
Is there any replace version or other js ui?

@Sell24
Copy link

Sell24 commented Aug 20, 2021

To remove this error until it is fixed, find the vue3-treeselect.common.js file in your node_modules folder and then comment out all lines that have "var h = this.$createElement;". There should be 27 of them as of this post.

@jamols09
Copy link

To remove this error until it is fixed, find the vue3-treeselect.common.js file in your node_modules folder and then comment out all lines that have "var h = this.$createElement;". There should be 27 of them as of this post.

Commented all of them on the code but the issue still shows up.
image

@jamols09
Copy link

To be honest it's been quite a while and the problem still exists. This is probably the best multiselect and only one with nested options I've ever used however its quite buggy. I really hope you give this some time so this would be fixed.

@ftb
Copy link

ftb commented Sep 1, 2021

HI! some news about this? It seems e blocking bugs...

@alessioraggioli
Copy link

alessioraggioli commented Sep 17, 2021

Same issue guys.. hope they will fix it because it's a great library!

Anyway, I have temporarely disabled warnings with this code on main.js (using Vue3)

const app = createApp(App)
app.config.errorHandler = () => null;
app.config.warnHandler = () => null;

@jamols09
Copy link

Same issue guys.. hope they will fix it because it's a great library!

Anyway, I have temporarely disabled warnings with this code on main.js (using Vue3)

const app = createApp(App)
app.config.errorHandler = () => null; app.config.warnHandler = () => null;

I dont think this is safe.

@alessioraggioli
Copy link

Same issue guys.. hope they will fix it because it's a great library!
Anyway, I have temporarely disabled warnings with this code on main.js (using Vue3)
const app = createApp(App)
app.config.errorHandler = () => null; app.config.warnHandler = () => null;

I dont think this is safe.

Infact is not.. I think I'm going to switch to another tree library, because is not possible to go in production with these warnings..

drummerroma added a commit to drummerroma/vue3-treeselect that referenced this issue Oct 23, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests