Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hot reload will cause Maximum recursive updates exceeded in <Form> #4119

Closed
2 of 5 tasks
bar-min opened this issue Feb 5, 2023 · 6 comments
Closed
2 of 5 tasks

Hot reload will cause Maximum recursive updates exceeded in <Form> #4119

bar-min opened this issue Feb 5, 2023 · 6 comments

Comments

@bar-min
Copy link

bar-min commented Feb 5, 2023

What happened?

If we place Field component in another component and use it in the Form, then after hot reload there will be an error.
(It will cause Maximum recursive updates exceeded in component)

Reproduction steps

  1. Go to demo
  2. Check TestField.vue component.
  3. Change text in console.log on line 13 to trigger hot reload
  4. 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

No response

Demo link

https://codesandbox.io/s/vee-validate-loop-tuzlmm

Code of Conduct

@hieutran094
Copy link

I have also faced this issue.

@mingtheanlay
Copy link

mingtheanlay commented Apr 4, 2023

Still having this issue

@antlionguard
Copy link

using useForm solves the problem.

@websitevirtuoso
Copy link

yes I have the same issue. Will try to use "useForm" to fix it

@websitevirtuoso
Copy link

using useForm solve the problem

@logaretm
Copy link
Owner

logaretm commented Jul 8, 2023

Does this happen with vite, vue and vee-validate all upgraded to latest versions? AFAIK it seems to happen with Webpack configurations on some versions of vue/vee-validate which may be a bug with the HMR with that setup and not with vee-validate itself.

P.S: I downloaded the example and it does not happen with vee-validate@4.9+ and vue3.2+ and does not happen with vite at all, the project setup is too old for me to investigate and support.

Closing until proof it happens on current releases and new ecosystem recommendations, especially since there is a workaround.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants