Warnings in console after ignore route in-component

[Jassmin586]

My app have got two languages (en and ar). To set only one language in specific page I used 'in-component' option:

nuxtI18n: {
    locales: ['en']
},

After that I have a page with only en language, that's great but also a lot of warnings in console like

How properly can I set one language for page without warnings?

[rchl]

This is probably triggered because you have language selector somewhere on the page that calls localePath or switchLocale with those other locales.

You'd need to show the code that triggers those warnings, then I might be able to advise more.

[Jassmin586]

I commented all localePath and switchLocale in project and still the same.

Simple reproduce:
https://codesandbox.io/s/710-nuxt-i18n-vqgsx?file=/pages/about.vue

Turn to Console and click 'About' link on homepage.

[rchl]

Could be also coming from seo functionality if you have that enabled.
But I will look into it later (can't right now).

[rchl]

Yes, those are triggered from seo functionality (seo: true).
I'll check later if I can do something about it.

For the record: the issue is due to disabling some locales per-route. In that case we don't keep track of which page has which locales disabled and so we assume that all locales are available.

[matsrietdijk]

@rchl this warning it triggered even more when seo: true, thats true. But the real issue is loadAndSetLocale which doesn't consider either filtering locale on the component as @Jassmin586 did above or the possiblilty of setting nuxtI18n: false on the component.

So even when disabling seo all together this warning will still be thrown on initial load and any time you programatically switch the locale with $i18n.setLocale(..) on a page configured like this.

[ozgurdemir]

Any updates on this? I'm running into the same issue. Probably related to this but I'd also like to remove the language switcher on pages which don't have that language enabled. It seems i18n does not have any variable stating which languages are actually available for the actual page.

[Menark]

The same issue.

[quangnhattran]

Looking for clear solution on this matter. I am getting similar warnings

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[HADB]

Any updates?

[gouz7514]

Any updates?

[pinecone-squirrel]

The problem remains unresolved

[BobbieGoede]

Closing this as v7 is not being actively worked on (critical hotfixes only), if this still applies to v8 and later please open a new issue!