-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
ERROR #8
Comments
yup, have the same issue. |
can you share your code? |
the example code provided on the readme |
working try check your |
I think it has to do with the vue router.
It looks like it's being loaded in there a least a hundred times. |
@diadal could you please provide working example code? Thanks! |
you need to make a clone of this to your than
use above as sample |
Thank you for your help! |
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
[Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://new-issue.vuejs.org/?repo=vuejs/vue-next
at <VueQr3 width=200 height=200 data="https://diadal.com.ng" ... >
at <VueQr3 width=200 height=200 data="https://diadal.com.ng" ... >
I followed the template and get that error. how to solve it?
runtime-core.esm-bundler.js:6142 Uncaught (in promise) RangeError: Maximum call stack size exceeded
at Function.keys ()
at exposeSetupStateOnRenderContext (runtime-core.esm-bundler.js:6142)
at handleSetupResult (runtime-core.esm-bundler.js:6370)
at setupStatefulComponent (runtime-core.esm-bundler.js:6339)
at setupComponent (runtime-core.esm-bundler.js:6273)
at mountComponent (runtime-core.esm-bundler.js:4125)
at processComponent (runtime-core.esm-bundler.js:4100)
at patch (runtime-core.esm-bundler.js:3695)
at mountChildren (runtime-core.esm-bundler.js:3891)
at mountElement (runtime-core.esm-bundler.js:3800)
The text was updated successfully, but these errors were encountered: