hot reload will cause Maximum recursive updates exceeded in component <Form>

[tbl0605]

What happened?

I get following error while using very simple custom field components:
[Vue warn]: Maximum recursive updates exceeded in component <Form>. This means you have a reactive effect that is mutating its own dependencies and thus recursively triggering itself. Possible sources include component template, render function, updated hook or watcher source function.

Reproduction steps

https://codesandbox.io/s/vee-validate-forked-lmxx59?file=/src/components/VeeInput.vue

1. Open file VeeInput.vue
2. modify file VeeInput.vue by writing some comment at line 7 and save the file
3. check console

Version

Vue.js 3.x and vee-validate 4.x

What browsers are you seeing the problem on?

• Firefox
• Chrome
• Safari
• Microsoft Edge

Relevant log output

[Vue warn]: Maximum recursive updates exceeded in component <Form>. This means you have a reactive effect that is mutating its own dependencies and thus recursively triggering itself. Possible sources include component template, render function, updated hook or watcher source function.

Demo link

https://codesandbox.io/s/vee-validate-forked-lmxx59

Code of Conduct

• I agree to follow this project's Code of Conduct

[logaretm]

I have downloaded the example locally and upgraded a few Vue dependencies and it seems to be working fine. Can you reproduce it on a vite installation with the latest versions for Vue and vee-validate and vite?

This is a duplicate of #4119 and closing for the same reason, I tried the same code in a vite project and it did not happen so I'm assuming it is an HMR bug with the no longer recommended webpack ecosystem.

[tbl0605]

Hi @logaretm,
thank you for looking at my bug report :)
I actually don't use webpack (but Vite), I just copied the test case (and adapted it) from bug report #3580, I was a bit lazy to create a test case from scratch ;)

With the latest versions for Vue, Vee-validate and Vite, the problem doesn't happen anymore with very simple forms, but sadly it still occurs with more complex forms and components. I will try to create another simple test case, but it will probably take me some time (my components got complicated meanwhile).

[logaretm]

Sure, let me know here and I will check it then.