Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How can I redirect translated url to the same page

See original GitHub issue

I want to translate url, but have an issue in ssr loading.
here is my configuration `

// nuxt.config.js
module.exports = {
...
modules: [
   [
      'nuxt-i18n',
      {
        seo: true,
        lazy: true,
        detectBrowserLanguage: {
          useCookie: true,
          cookieKey: 'i18n_redirected',
          alwaysRedirect: false,
          fallbackLocale: 'hy'
        },
        locales: [
          {
            name: 'English',
            code: 'en',
            iso: 'en-US',
            file: 'en.json'
          },
          {
            name: 'Հայերեն',
            code: 'hy',
            iso: 'hy-AM',
            file: 'hy.json'
          }
        ],
        langDir: 'locales/',
        defaultLocale: 'hy',
        parsePages: false,
         pages: {
           about: {
             en: '/about',
             hy: '/մեր֊մասին'
           },
       }
   ]
}

it works in client side when i link to localePath(‘about’) . but when i refresh my page it cant find http://localhost:4000/մեր֊մասին

Issue Analytics

State:
Created 3 years ago
Comments:11

Top GitHub Comments

1reaction

rchlcommented, Mar 25, 2021

The removal of encodePaths is almost a year old.

At the time the removal made sense as VueRouter didn’t expect encoded paths.

If you have an issue now because VueRouter and Nuxt made changes then feel free to report an issue about it with proper reproduction steps and it will be fixed.

1reaction

rchlcommented, May 25, 2020

Paths encoding was fixing issue #7 but that one doesn’t reproduce in latest Nuxt anymore so I’m even more confident in getting rid of encodePaths option.