Skip to content

Maximum recursive updates exceeded in component <ProseCodeTree> #5828

Closed

Description

@stijns96

Environment

Operating system macOS 23.4.0
CPU Apple M1 (8 cores)
Node.js version v22.15.0
nuxt/cli version 3.31.3
Package manager pnpm@10.11.0
Nuxt version 4.2.2
Nitro version 2.12.9
Builder vite@7.3.0
Config compatibilityDate, css, devtools, mdc, modules, nitro, routeRules, runtimeConfig, site
Modules @nuxt/eslint@1.12.1, @nuxtjs/seo@3.3.0, @nuxt/ui@4.3.0, @nuxt/content@3.10.0, @nuxt/image@2.0.0, nuxt-auth-utils@0.5.26

Is this bug related to Nuxt or Vue?

Nuxt

Package

v4.x

Version

v4.3.0

Reproduction

Description

I try to render markdown with the MDC component in my custom content component. For some reason I'm getting this error when I try to change tabs.

Image

Additional context

Preferably I'll use the <ProseCodeTree> component, but I can't easily get this to work.

Logs

Uncaught (in promise) Maximum recursive updates exceeded in component <ProseCodeTree>. This means you have a reactive effect that is mutating its own dependencies and thus recursively triggering itself. Possible sources include component template, render function, updated hook or watcher source function.

Activity

  1. added
    bugSomething isn't working
    triageAwaiting initial review and prioritization
    on Jan 7, 2026
  2. stijns96 commented on Jan 7, 2026

    @stijns96
    ContributorAuthor

    Going back to v4.2.0 fixed the issue

  3. benjamincanac commented on Jan 7, 2026

    @benjamincanac
    Member

    Can you provide a reproduction or copy-past an example? I don't reproduce this anywhere.

  4. github-actions commented on Jan 7, 2026

    @github-actions

    Would you be able to provide a reproduction? 🙏

    More info

    Why do I need to provide a reproduction?

    Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

    What will happen?

    If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect.

    If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), they will be closed automatically after a while. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

    How can I create a reproduction?

    We have templates to create a minimal reproduction:

    Please ensure that the reproduction is as minimal as possible. See more details in our guide.

    You might also find these other articles interesting and/or helpful:

  5. stijns96 commented on Jan 7, 2026

    @stijns96
    ContributorAuthor

    Trying to but constantly getting this error when adding @nuxt/content to the modules

     ERROR  SQLITE_BUSY: database is locked                                                                                                                  19:16:59
    
        at sqliteError (node_modules/.pnpm/sqlite3@5.1.7/node_modules/sqlite3/lib/sqlite3.pure.js:1:94706)
        at 51656 (node_modules/.pnpm/sqlite3@5.1.7/node_modules/sqlite3/lib/sqlite3.pure.js:1:12557)
        at _emscripten_asm_const_int (node_modules/.pnpm/sqlite3@5.1.7/node_modules/sqlite3/lib/sqlite3.pure.js:1:84040)
        at ccall (node_modules/.pnpm/sqlite3@5.1.7/node_modules/sqlite3/lib/sqlite3.pure.js:1:5494)
        at Object.eval (node_modules/.pnpm/sqlite3@5.1.7/node_modules/sqlite3/lib/sqlite3.pure.js:1:5844)
        at eval (node_modules/.pnpm/sqlite3@5.1.7/node_modules/sqlite3/lib/pure/database.js:86:26)
        at processTicksAndRejections (node:internal/process/task_queues:196:998)
        at _0x308632 (https://githubgwzefm4w-emh2.w-credentialless-staticblitz.com/blitz.365214aa.js:31:534946) 
    
    
    
     ERROR  SQLITE_BUSY: database is locked    

    https://stackblitz.com/edit/github-gwzefm4w

  6. added a commit that references this issue on Jan 16, 2026
    c79cb77
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingneeds reproductiontriageAwaiting initial review and prioritizationv4#4488

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions