#Nuxt Studio issues

4 messages · Page 1 of 1 (latest)

pseudo trellis
#

Had a few issues with the package.

  1. It was not letting me access the /_studio route, even after a successful login. I had to add this to nuxt config: vite.optimizeDeps.include = ['brace-expansion'].
    The button to open the studio panel showed up after this.
    (nuxt content issue: 3306)

  2. When the panel is open, the content files are there, but they have no content inside when opened.

  3. It shows warnings on the console, multiple times:

[intlify] Not found 'studio.tooltips.toggleStudio' key in 'en' locale messages.
[intlify] Not found 'studio.nav.public' key in 'en' locale messages.

For context, I'm running "nuxt": "^4.2.1", "nuxt-studio": "^1.0.0-alpha.2", "@nuxt/content": "^3.8.2", "@nuxtjs/i18n": "^10.2.1", and other packages. Also, I have two languages setup for nuxt/i18n.

sacred violetBOT
#

Hi @pseudo trellis. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:

#

There’s no mention of nuxt-studio or these specific Studio issues in the provided knowledge sources, so I can’t give a definitive, source‑backed fix for your case.

From the documents we do have:

  • Similar i18n “Not found key … in locale messages” warnings are caused by missing translation keys or by mis‑placed i18n configuration, and are resolved by putting the correct i18n config in nuxt.config.ts and/or using an external i18n.config.ts referenced via i18n.vueI18n.Localization answeri18n browser detection
  • Nuxt 4.x + modules can have subtle integration issues (e.g. order of @nuxt/ui and @nuxt/content, Vite optimizeDeps quirks, etc.), and workarounds often involve adding entries to vite.optimizeDeps.include or downgrading Nuxt temporarily.Nuxt UI installationNuxt 4.20 CommonJS

However, there is no specific documentation in the sources about:

  • nuxt-studio requiring brace-expansion in vite.optimizeDeps.include
  • Studio’s / _studio panel showing empty content files
  • The exact studio.* i18n keys or how Studio expects them to be wired when you already use @nuxtjs/i18n

So:

  • Your workaround for (1) with vite.optimizeDeps.include = ['brace-expansion'] isn’t covered in the sources but is consistent with similar Vite optimizeDeps issues.
  • For (2) and (3), the sources don’t describe any known Studio bug or configuration requirement that would explain empty documents or the missing studio.* i18n keys.

Given that, the best I can say, based strictly on the provided material, is:

#
  • Check your i18n setup matches the documented pattern: global i18n options (locales, defaultLocale, detectBrowserLanguage, etc.) in nuxt.config.ts and the Vue I18n runtime config in a separate i18n.config.ts referenced as i18n.vueI18n = './i18n.config.ts'.i18n 3.8.0 fixLocalization answer This type of misplacement can cause unexpected i18n behavior and warnings.
  • Be aware Nuxt 4.2.x has had some module and Vite integration regressions, and users sometimes resolve them only by downgrading to an earlier 4.1.x version while waiting for a fix.Nuxt 4.20 CommonJS

Beyond that, the knowledge sources simply don’t contain enough about nuxt-studio to confidently explain or resolve your three points.

Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: