Nuxt•11h ago

Prerender with I18n differentDomain and strategy: prefix_except_default

Let's say we have 3 locales: test.com, test.com/de, test.nl. As you may see we do have 2 homepages with the same route: / but within a different domain. Is it possible to prerender both pages?

5 Replies

kapa.ai•11h ago

Hi @vanhunselm. 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 specific information about prerendering multiple homepages with different domains using i18n and the differentDomain strategy. However, I can provide some general guidance on prerendering in Nuxt that might be helpful for your scenario. Nuxt offers several ways to prerender routes, including: 1. Using the nuxi generate command, which crawls your site and prerenders linked pages Prerendering. 2. Manually specifying routes to prerender in your nuxt.config.ts file Prerendering. 3. Using defineRouteRules at the page level to set prerendering rules defineRouteRules. 4. Using the prerenderRoutes utility within your Nuxt application prerenderRoutes. For your specific case with multiple domains, you might need to combine these approaches. Here's a suggestion: 1. In your nuxt.config.ts, you could try specifying the routes explicitly:

export default defineNuxtConfig({
  nitro: {
    prerender: {
      routes: ['/', '/de', '<https://test.nl/']>
    }
  }
})

export default defineNuxtConfig({
  nitro: {
    prerender: {
      routes: ['/', '/de', '<https://test.nl/']>
    }
  }
})

2. You might also need to use the prerenderRoutes utility in your application code to ensure all necessary routes are prerendered:

prerenderRoutes(['/', '/de', '<https://test.nl/']>)

prerenderRoutes(['/', '/de', '<https://test.nl/']>)

However, it's important to note that the effectiveness of these approaches might depend on how your i18n setup and domain configuration are implemented. The provided knowledge sources don't contain specific information about prerendering with i18n and different domains, so you might need to experiment or consult the Nuxt and i18n plugin documentation for more detailed guidance. If you need more specific information or a guaranteed solution, I recommend checking the official Nuxt documentation or asking in the Nuxt community forums where you might find users who have implemented similar setups. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•11h ago

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

vanhunselmOP•10h ago

@kapa.ai '<https://test.nl/' doesn't seem to work

kapa.ai•10h ago

Let me check the knowledge base for you again. One moment! :books: ---------------------- I apologize for the confusion in my previous response. You're right that the URL format I suggested doesn't work for prerendering. Let me provide a more accurate answer based on the available information. The knowledge sources don't contain specific information about prerendering multiple domains with i18n using the differentDomain strategy. However, we can infer some general principles about prerendering in Nuxt. For prerendering in Nuxt, you typically specify routes relative to the root of your application, not full URLs. The nitro.prerender.routes option in your nuxt.config.ts expects relative paths. Given your scenario with test.com, test.com/de, and test.nl, you might try something like this in your nuxt.config.ts:

export default defineNuxtConfig({
  nitro: {
    prerender: {
      routes: ['/', '/de']
    }
  }
})

export default defineNuxtConfig({
  nitro: {
    prerender: {
      routes: ['/', '/de']
    }
  }
})

This configuration would prerender the root route / (which could correspond to test.com) and /de (for test.com/de). However, for the separate domain test.nl, the situation is more complex. Nuxt's built-in prerendering doesn't have a straightforward way to handle multiple domains in a single build process. You might need to consider alternative approaches, such as: 1. Separate builds for each domain. 2. Custom build scripts that run the prerendering process multiple times with different configurations. 3. Using server-side rendering (SSR) for the multi-domain setup instead of static prerendering. For a more definitive solution to your specific use case with i18n and multiple domains, I recommend: 1. Checking the Nuxt i18n module documentation for any advanced configurations that might help. 2. Posting a question in the Nuxt GitHub discussions or Nuxt Discord community, where you might find users who have implemented similar setups. Remember, the effectiveness of any solution will depend on your specific i18n setup and how you've configured the different domains in your Nuxt application. Link title ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

kapa.ai•10h ago

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

Gaming

Programming

Prerender with I18n differentDomain and strategy: prefix_except_default

Did you find this page helpful?