Possible to deactivate automatic json files generation on a route basis

[Buzut]

Hi there!

I'm in a situation where I created a bunch of content pages (50 or so) and none of these need the external JSON translation files.
I'd like to avoid having all these unused empty translation files if possible (more than 400 empty json files in this case with 7 locales 😅).

Couldn't find in the doc whether possible or not. I was picturing an option like localeOnly in defineI18nRoute. Open to any suggestion.

[s00d]

https://s00d.github.io/nuxt-i18n-micro/guide/getting-started#%F0%9F%94%84-disablepagelocales

[Buzut]

Yeah, had seen this one, but it's a global. So this would disable translation files for all routes.
I just wanted to know if there was a way to opt-out on a case by case basis, not globally :)

[s00d]

no

[Buzut]

Technically not possible due to the architecture or just not implemented? In the latter case I can take a look 🤔

[s00d]

just not implemented

[Buzut]

I'll try and take a look at it when I have some free time. Never checked how modules work under the hood…
In the meantime, I excluded the unwanted files from git as well as hidden then VScode, so it's as if they weren't there.

Thanks for your help Pavel!

[Buzut]

As it's partially related, if one were to use the disablepagelocales feature.

Are there any drawvbacks (perf related maybe) of having all but global translations directly in the SFC? Or is it just a matter of preference?

[s00d]

The more translations you have in components, the slower everything will work. Translations in components are mainly useful for solving issues when switching to i18n for components published on npm. I wouldn’t recommend using them in your own project at all.

[Buzut]

Thanks for clarifying this out! Still a viable solution for translations specific to a component though (in case the component is on multiple pages but not global either).

Or should we really strive to avoid it at all costs? I think I'll clary this in the docs if you're ok for a PR on the matter :)

[s00d]

You don't have to avoid it, but the problem is that duplicate text in page-by-page translations will work better than translations within components. It's up to you to decide what matters more to you—performance or structure.
Yes, you can add this to the documentation.