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

Maximum call stack size exceeded when passing global component through slot in a local component with same name #6027

kfras opened this issue May 30, 2022 · 0 comments


Copy link

kfras commented May 30, 2022

Vue version


Link to minimal reproduction

Steps to reproduce

  • Register a global component (eg. something.vue)
  • Create a local component with the same name as the global component
  • Create another component with a slot in it (eg. component-with-slot.vue)
  • Within the local component, add the component with a slot, and then pass the global component through the slot

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

  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
  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
  Chrome: 101.0.4951.64
  Safari: 15.3

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.

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

No branches or pull requests

2 participants