fix(i18n): pass scope to components

[BobbieGoede]

This prevents these warning logs:

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ready	Preview, Comment	Jan 29, 2026 7:48pm
npmx.dev	Ready	Preview, Comment	Jan 29, 2026 7:48pm

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
npmx-lunaria	Ignored		Jan 29, 2026 7:48pm

[userquin]

shouldn't be global if not specified? at elk.zone we don't have any i18n-t with scope global 🤔

[BobbieGoede]

@userquin yeah it falls back to global by default, this is just to get rid of the warnings

[cernymatej]

@BobbieGoede potentially a suggestion for a breaking change, but why isn't global the default (and not just a fallback) - i.e. no wraning?
I personally never use local scopes at all and I think that most users don't either. (might be mistaken, though...)

[BobbieGoede]

@cernymatej this behavior is from vue-i18n, by default the scope is inherited from its parent which could be global or local.

I think the warning was added because this behavior was confusing, without making a breaking change. I agree that a static default scope would probably be more intuitive.