Composition API mode: Why using the Global Scope (or not)?

[gagarine]

The documentation regarding the global scope is not clear to me: https://vue-i18n.intlify.dev/guide/advanced/composition.html#global-scope

The above code sets the useI18n option to useScope: 'global', which allows useI18n to return a Composer instance that can be accessed by the i18n instance global property. This allows useI18n to return the Composer instance that can be accessed by i18n instanceglobal property, which is a global scope. The Composer instance is a global scope.

The only problem would be a conflict with another lib that also want to use the global scope? In that case why pushing so many property in the global scope instead of only $i18n and then wrap everything under that?

Calling useI18n() in setup will create a new instance each time? Or it's the same instance and have no performance penalties compared to the global scope?

[gagarine]

The answer is in another part of the documentation https://vue-i18n.intlify.dev/guide/essentials/scope.html

The local scope allows you to apply scopes on each component basis like the <style scoped> of single-file components, only that component’s scope is enabled. This is very useful if you want to manage the i18n resource like locale messages for each component.