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

Freezes up in Nuxt Content #150

Closed
kbrgmn opened this issue Apr 2, 2024 · 1 comment
Closed

Freezes up in Nuxt Content #150

kbrgmn opened this issue Apr 2, 2024 · 1 comment

Comments

@kbrgmn
Copy link

kbrgmn commented Apr 2, 2024

Environment

  • Operating System: Linux
  • Node Version: v21.7.1
  • Nuxt Version: 3.11.1
  • CLI Version: 3.11.1
  • Nitro Version: 2.9.5
  • Package Manager: bun@1.1.0
  • Builder: -
  • User Config: devtools, modules
  • Runtime Modules: @nuxt/content@2.12.1, nuxt-icon@0.6.10
  • Build Modules: -

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:

  • a single page [...slug].vue:
<template>
    <ContentDoc/>
</template>`)
  • 2 components

the first of which is:

<template>
    <Icon name="heroicons:information-circle"/>
</template>

the second component is:

<template>
    <div>
        <p>Different component here</p>
        <div>
            <slot/>
        </div>
    </div>
</template>
  • 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.

@kbrgmn
Copy link
Author

kbrgmn commented Jun 26, 2024

Seems to be fixed by now

@kbrgmn kbrgmn closed this as completed Jun 26, 2024
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

1 participant