We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
^3.2.34
https://stackblitz.com/edit/vitejs-vite-kr255h?file=src%2FApp.vue&terminal=dev
On 3.2.33 and prior, this would render the global component just as if the component would be rendered if it wasn't passed through a slot.
The global component won't render, and the following error occurs Uncaught RangeError: Maximum call stack size exceeded
Uncaught RangeError: Maximum call stack size exceeded
System: OS: macOS 12.2 CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz Memory: 21.71 MB / 16.00 GB Shell: 5.8 - /bin/zsh Binaries: Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node Yarn: 1.22.17 - /usr/local/bin/yarn npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm Browsers: Chrome: 101.0.4951.64 Safari: 15.3
This is not a duplicate of #5965. Issue #5965 specifically address the problem relating to component names conflicting with native HTML elements.
The text was updated successfully, but these errors were encountered:
9734b31
No branches or pull requests
Vue version
^3.2.34
Link to minimal reproduction
https://stackblitz.com/edit/vitejs-vite-kr255h?file=src%2FApp.vue&terminal=dev
Steps to reproduce
What is expected?
On 3.2.33 and prior, this would render the global component just as if the component would be rendered if it wasn't passed through a slot.
What is actually happening?
The global component won't render, and the following error occurs
Uncaught RangeError: Maximum call stack size exceeded
System Info
Any additional comments?
This is not a duplicate of #5965. Issue #5965 specifically address the problem relating to component names conflicting with native HTML elements.
The text was updated successfully, but these errors were encountered: