Bump i18next from 24.2.2 to 25.6.0 in /enatega-multivendor-web

[dependabot]

Bumps i18next from 24.2.2 to 25.6.0.

Release notes

Sourced from i18next's releases.

v25.6.0

• feat: exists() method now respects returnObjects option - returns false when accessing an object key with returnObjects: false, enabling detection of object vs string keys 2359

  Note: This is a potential behavior change. If you were previously calling exists() with returnObjects: false on object keys, those calls will now return false instead of true. This enables developers to detect whether a key points to an object or string value.

v25.5.3

• export esm type declaration for keyFromSelector 2356

v25.5.2

• fix last change => for cjs there is just 1 default export, no named exports, fixes 2348

v25.5.1

• export keyFromSelector from index.cjs 2347

v25.5.0

• export keyFromSelector function for testing purposes 2346

v25.4.2

• fix: enableSelector: true doesn't work with custom keySeparator 2341

v25.4.1

• fix: KeyPrefix not working with new selector api 2340

v25.4.0

• add new selector API to improve TypeScript IDE performance 2322
  • To enable it, set enableSelector: true in your configuration options
  • With enableSelector: "optimize", i18next can now handle translation dictionaries of any size, without affecting IDE performance or build times
  • To assist with the migration, we've published the following packages:
    • @​i18next-selector/codemod
    • @​i18next-selector/vite-plugin

v25.3.6

• improve fix: Ordinals and non-ordinals don't work together 2337

v25.3.5

• fix: Ordinals and non-ordinals don't work together 2337

v25.3.4

• remove unnecessary debug logs

v25.3.3

• fix: Brackets breaking nesting interpolation 2336

v25.3.2

• fix dir() for non-Intl language codes 2330

v25.3.1

• warn if legacy interpolation.format function is still used

v25.3.0

... (truncated)

Changelog

Sourced from i18next's changelog.

25.6.0

• feat: exists() method now respects returnObjects option - returns false when accessing an object key with returnObjects: false, enabling detection of object vs string keys 2359

  Note: This is a potential behavior change. If you were previously calling exists() with returnObjects: false on object keys, those calls will now return false instead of true. This enables developers to detect whether a key points to an object or string value.

25.5.3

• export esm type declaration for keyFromSelector 2356

25.5.2

• fix last change => for cjs there is just 1 default export, no named exports, fixes 2348

25.5.1

• export keyFromSelector from index.cjs 2347

25.5.0

• export keyFromSelector function for testing purposes 2346

25.4.2

• fix: enableSelector: true doesn't work with custom keySeparator 2341

25.4.1

• fix: KeyPrefix not working with new selector api 2340

25.4.0

• add new selector API to improve TypeScript IDE performance 2322
  • To enable it, set enableSelector: true in your configuration options
  • With enableSelector: "optimize", i18next can now handle translation dictionaries of any size, without affecting IDE performance or build times
  • To assist with the migration, we've published the following packages:
    • @​i18next-selector/codemod
    • @​i18next-selector/vite-plugin

25.3.6

• improve fix: Ordinals and non-ordinals don't work together 2337

25.3.5

• fix: Ordinals and non-ordinals don't work together 2337

25.3.4

• remove unnecessary debug logs

... (truncated)

Commits

• 7484e96 25.6.0
• bb7d062 exists with returnObjects false, should address #2359
• 863dc0c 25.5.3
• c8cc717 changelog
• 349b70c fix: export esm type declaration for keyFromSelector (#2356)
• a618e98 25.5.2
• 57da108 for cjs there is just 1 default export, no named exports, fixes #2348
• 83353ba 25.5.1
• cbd3ba2 release
• 912a8ec exports keyFromSelector for CommonJS (#2347)
• Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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.