Skip to content

bug: Using @nuxtjs/i18n with specific configuration makes Compodium not render components #171

Description

@krlctrl

Description

In Nuxt project using @nuxtjs/i18n module with a specific configuration (described in reproduction section) makes unable to render components in the Compodium devtools.

Logs in terminal:

 WARN  [Vue Router warn]: No match found for location with path "/__compodium__/renderer"

Errors is the browser console:

GET http://localhost:3000/__compodium__/renderer NS_ERROR_XFO_VIOLATION
GET http://localhost:3000/__compodium__/renderer Status 404 Page not found: /__compodium__/renderer

Reproduction

Relevant dependency versions:

  • nuxt: ^4.4.2
  • @nuxtjs/i18n: ^10.2.4
  • @nuxt/ui: ^4.6.0 (not required, but just to have some components to test)
  • @compodium/nuxt: 0.1.0-beta.12

Example nuxt.config.ts, important part is the i18n section:

// https://nuxt.com/docs/api/configuration/nuxt-config
export default defineNuxtConfig({
  compatibilityDate: "2025-07-15",
  modules: ["@compodium/nuxt", "@nuxt/ui", "@nuxtjs/i18n"],
  devtools: { enabled: true },
  css: ["~/assets/css/main.css"],
  i18n: {
    defaultLocale: "en",
    strategy: "prefix",
    locales: [
      { code: "en", language: "en-GB", name: "English", file: "en.json" },
    ],
  },
});

It's also important to use Nuxt Pages feature, meaning that pages folder needs to exist with at least index.vue page (pages/index.vue`).

The problematic configurations are i18n.strategy being "prefix" and having at least one i18n.locales added. Using different strategy like "prefix_except_default" won't trigger the problem.

To get the errors, start dev server and open the Compodium from the Nuxt devtools in the Browser.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions