Nuxt•5d ago

checking routes with i18n - report usage

Hello, Does anyone have a method to verify all the routes for pages that use defineI18nRoute and could generate something like this:

defineI18nRoute({
    paths: {
      en: '/search', 
      fr: '/rechercher'
    }
  })

defineI18nRoute({
    paths: {
      en: '/search', 
      fr: '/rechercher'
    }
  })

I have 20 different pages, including pages with dynamic IDs, and some that does not rely on defineI18nRoute. I’d like to check all possible route combinations in a single report. Thanks !

3 Replies

kapa.ai•5d ago

Hi @gabrielstuff. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave: ---------------------- Based on the knowledge sources provided, there isn't a direct method or tool mentioned specifically for verifying all routes that use defineI18nRoute and generating a comprehensive report as you've described. However, I can suggest a potential approach using some of Nuxt's experimental features that might help you achieve something similar. The Nuxt documentation on experimental features mentions an experimental feature called scanPageMeta that allows exposing some route metadata defined in definePageMeta at build-time to modules. While this doesn't directly address defineI18nRoute, it could potentially be adapted for your needs. To use this feature, you would need to enable it in your nuxt.config.ts:

export default defineNuxtConfig({
  experimental: {
    scanPageMeta: true
  }
})

export default defineNuxtConfig({
  experimental: {
    scanPageMeta: true
  }
})

Then, you could use the pages:extend hook to access the route information:

export default defineNuxtConfig({
  experimental: {
    scanPageMeta: true
  },
  hooks: {
    'pages:extend' (routes) {
      console.log(routes)
      // Here you could implement your custom logic to generate a report
    }
  }
})

export default defineNuxtConfig({
  experimental: {
    scanPageMeta: true
  },
  hooks: {
    'pages:extend' (routes) {
      console.log(routes)
      // Here you could implement your custom logic to generate a report
    }
  }
})

This approach would allow you to access route information at build time, which you could then use to create a custom report. However, it's important to note that this is an experimental feature and may not capture all the information you need, especially for routes defined using defineI18nRoute. For a more comprehensive solution, you might need to create a custom Nuxt module that analyzes your pages and their i18n configurations. This would involve parsing your Vue files and extracting the defineI18nRoute configurations. Unfortunately, the knowledge sources don't provide a ready-made solution for your specific requirement. You might want to consider asking this question in the Nuxt community forums or GitHub issues, as there might be community-created tools or more recent developments that address this need. Nuxt Experimental Features Documentation ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•5d ago

<@213659913149218817> Kapa.ai is still learning and improving, please let me know how I did by reacting below.

gabrielstuffOP•5d ago

Ok I will test

Gaming

Programming

checking routes with i18n - report usage

Did you find this page helpful?