Bump react-i18next from 10.13.2 to 16.6.1 in /enatega-multivendor-admin

[dependabot]

Bumps react-i18next from 10.13.2 to 16.6.1.

Changelog

Sourced from react-i18next's changelog.

16.6.1

• feat(types): i18nKey of <Trans i18nKey={sk} /> to accept a SelectorKey 2364

16.6.0

• warn when t is called before ready with useSuspense: false 1896
• type-safe values prop on <Trans /> component — interpolation variables are now inferred from the translation string when custom types are configured 1772

16.5.8

• A selector function cannot be resolved without an i18n instance... returning empty string is safer than leaking the raw function reference. 1907

16.5.7

• fix: <Trans> component with enableSelector: true does not support multiple selectors for fallbacks 1907

16.5.6

• fix: prevent crash in useSSR when init() hasn't been called before useSSR — now logs a warning instead of throwing 1604

16.5.5

• fix: prevent crash in useSSR, getInitialProps and Translation when no i18next instance is available (e.g. in monorepo setups with duplicate react-i18next copies) — now logs a clear warning instead of throwing 1604

16.5.4

• fix: Overriding React component props not working 1902

16.5.3

• fix: Trans named tags with underscore 1901

16.5.2

• fix: Type errors when you've declared a resources type 1899 via 1900

16.5.1

• fix: export nodesToString (runtime + TypeScript typings) to support i18next-cli (i18next/i18next-cli#155)

16.5.0

• Add configuration option transDefaultProps to set default props for the Trans component (e.g. tOptions, shouldUnescape, values) 1895

16.4.1

• fix(Trans): prevent double-escaping of interpolated values in component props (e.g. title). Unescape HTML entities before passing prop values to React to avoid rendered output like " / &[#39](https://github.com/i18next/react-i18next/issues/39);. 1893

16.4.0

... (truncated)

Commits

• 683156b 16.6.1
• 723d84b feat(types): i18nKey of \<Trans i18nKey={sk} /> to accept a SelectorKey
• 5c9f9f0 update i18next dep
• 3a68a0b 16.6.0
• 87eac5f type-safe values prop on \<Trans /> component — interpolation variables ar...
• 5228855 warn when t is called before ready with useSuspense: false #1896
• a75ef78 update deps and adjust tests
• b00adfa 16.5.8
• e367522 A selector function cannot be resolved without an i18n instance... returning ...
• 1cbd152 16.5.7
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by adrai, a new releaser for react-i18next since your current version.

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.