v5.2.0

What's Changed

• fix: types in $t by @cany748 in #24
  • TypeScript: also suggest keys with my-namespace: prefixes for $t

New Contributors

• @cany748 made their first contribution in #24

Full Changelog: v5.1.0...v5.2.0

v5.1.0

🚀Feature

Make useTranslation() available in Pinia and other app.runWithContext() cases #25

We use app-level provide/inject now to make the necessary internal i18next-vue things available. Pinia invokes all stores with app.runWithContext(), allowing useTranslation() to work there, too.

Thanks to @edikdeisling for suggesting this improvement!

v5.0.0

Version 5.0 changes the way we augment Vue types for the global $t and $i18next variables. This is a breaking change for some setups.

There are no new features, just this change and updated dependencies.

Migration from v4.x

(Re-phrasing the Vue Router changelog for an analogous change):

This release replaces declare module '@vue/runtime-core' with declare module 'vue' like it's supposed to be. If you (or packages you use) are also augmenting @vue/runtime-core, you will likely have to change it to vue. It is also recommended to use an up-to-date TypeScript version (>=5.4) and "moduleResolution": "Bundler" in your tsconfig.json.

No other changes/migration necessary.

Migration from v3.x

See the updated documentation for the exact breaking changes and upgrade information.

What's Changed

• Fix typescript module augmentation by @FlorianBruckner in #22

New Contributors

• @FlorianBruckner made their first contribution in #22

Full Changelog: v4.0.0...v5.0.0

v4.0.0

Version 4.0 removes the previously deprecated support for i18nOptions. There are no new features. Updating will save you some bytes :)

Migration from v3.x

See the updated documentation for the exact breaking changes and upgrade information.

v4.0.0-rc.1

Version 4.0 removes the previously deprecated support for i18nOptions. There are no new features. Updating will save you some bytes :)

Migration from v3.x

See the updated documentation for the exact breaking changes and upgrade information.

v3.0.0

Version 3 improves Composition API support and removes some legacy functionality & code.

Migration from v2.x

See the updated documentation for breaking changes, upgrade information and new features.

If you have feedback about the changes, you are welcome to leave a comment on #16.

v3.0.0-rc.1

Version 3 improves Composition API support and removes some legacy functionality & code.

Migration from v2.x

See https://i18next.github.io/i18next-vue/migration-v3.html for breaking changes, upgrade information and new features.

If you have feedback about the changes, you are welcome to leave a comment on #16.

Use

To run this version in your code, use

npm install i18next-vue@next

v3.0.0-alpha.1

Feedback welcome for version 3 draft

This is an early draft, how v3 of i18next-vue could look like.

Head over to #16 for an overview of the (breaking) changes.

Please leave a comment there, if the proposed changes look good to you, or if some of the changed/removed functionality would make an upgrade to v3 hard for you.

To test this version in your code, use

npm install i18next-vue@next

Changes compared to alpha.0

• restored support for i18nOptions under a new boolean legacyI18nOptionsSupport plugin option
  • support for lng, keyPrefix and namespaces
  • messages remains unsupported
  • support will be dropped in version 4
  • allows converting components incrementally over to useTranslation() with the respective options to get a specific t() function
• restored namespace loading for $t and useTranslation

v3.0.0-alpha.0

Feedback welcome for version 3 draft

This is a first draft, how v3 of i18next-vue could look like.

Head over to #16 for an overview of the (breaking) changes.

Please leave a comment there, if the proposed changes look good to you, or if some of the changed/removed functionality would make an upgrade to v3 hard for you.

To test this version in your code, use

npm install i18next-vue@next

v2.2.1

Bug Fixes

• Make $t and $i18next types work more reliably in Vue templates.
  • This should fix some situations where VS Code would not pick up the type definitions.