You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1 single simple content markdown page using the two components:
# Issue reproduction
First component (icon):
::ComponentWithIcon
::
::SecondComponent
We have some more content here
- nsetetur sadipscing elitr,
::
Describe the bug
When the page is visited (in dev mode with bun dev), it completely freezes up (both Firefox and Chrome),
with no text being selectable, developer console not opening if it hasn't already been opened or opening blank, browser not even closing properly, and this warning is printed hundreds of times repeatedly in the console:
Avoid app logic that relies on enumerating keys on a component instance.
The keys will be empty in production mode to avoid performance overhead.
(the reproduction does not have a single <script> tag in the whole repository)
However, this issue does not occur when a production build is being done with bun run build. When the first component (the nuxt-icon) is removed, the issue does not occur.
Logs
No warnings / errors are outputted in the terminal where nuxt dev is run.
The text was updated successfully, but these errors were encountered:
Environment
Reproduction
GitHub repo here: https://github.com/kbrgmn/nuxt-content-icon-reproduction (as the browser freezes/crashes, stackblitz does not work well here)
Very minimal reproduction:
[...slug].vue
:the first of which is:
the second component is:
Describe the bug
When the page is visited (in dev mode with
bun dev
), it completely freezes up (both Firefox and Chrome),with no text being selectable, developer console not opening if it hasn't already been opened or opening blank, browser not even closing properly, and this warning is printed hundreds of times repeatedly in the console:
(the reproduction does not have a single <script> tag in the whole repository)
However, this issue does not occur when a production build is being done with
bun run build
.When the first component (the nuxt-icon) is removed, the issue does not occur.
Logs
No warnings / errors are outputted in the terminal where
nuxt dev
is run.The text was updated successfully, but these errors were encountered: