Frederik Held

I second @vankeer on this and I think that SemVer shouldn't just be considered but adhered to. Here's what's written in the npm docs about SemVer: https://docs.npmjs.com/about-semantic-versioning Although they avoid...

So what's missing from the code I already posted?

https://stackblitz.com/edit/bobbiegoede-nuxt-i18n-starter-za36nq?file=components%2FLangSwitcher.vue I used your starter template. I copy & pasted the code from `app.vue` into `error.vue` and it already shows --> locale switcher links are broken Both pages use the...

The same as everywhere else. I use the same top bar for all pages, so I expect the language switcher to work everywhere the same. The error is just a...

Ah, that makes sense. TBH I'm not a fan of all the crude magic going on inside Nuxt. In Vue I would just have defined a catchall route in the...

> catch all route would only be used for non existent pages But a catchall is different from an error page. Catchall will send 200 for pages that should send...

> I agree they're different, but it would resolve the issue of the language switcher not working. The package ist called `nuxt-i18n`. So I expect it to work with Nuxt....

I want to be able to switch languages, even on the error page. If the user is on the non-existing route `/en/foo` and they switch to `de`, the route should...

> If a route exists in one language then it does work the way you describe, which ironically is actually an issue for other users, see https://github.com/nuxt-modules/i18n/issues/2782. I see the...

That would be a great new feature. I just had to write my own rgb to hex converter to be able to use the css color variables of my project's...