[Snyk] Upgrade i18next from 25.3.2 to 25.6.0 #280
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to upgrade i18next from 25.3.2 to 25.6.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 12 versions ahead of your current version.
The recommended version was released 24 days ago.
Issues fixed by the recommended upgrade:
SNYK-JS-AXIOS-12613773
SNYK-JS-FORMDATA-10841150
Release notes
Package name: i18next
-
25.6.0 - 2025-10-10
-
-
25.5.3 - 2025-10-01
- export esm type declaration for keyFromSelector 2356
-
25.5.2 - 2025-09-05
- fix last change => for cjs there is just 1 default export, no named exports, fixes 2348
-
25.5.1 - 2025-09-05
- export keyFromSelector from index.cjs 2347
-
25.5.0 - 2025-09-04
- export keyFromSelector function for testing purposes 2346
-
25.4.2 - 2025-08-24
- fix: enableSelector: true doesn't work with custom keySeparator 2341
-
25.4.1 - 2025-08-23
- fix: KeyPrefix not working with new selector api 2340
-
25.4.0 - 2025-08-20
- add new selector API to improve TypeScript IDE performance 2322
- To enable it, set
- With
- To assist with the migration, we've published the following packages:
- @ i18next-selector/codemod
- @ i18next-selector/vite-plugin
-
25.3.6 - 2025-08-14
- improve fix: Ordinals and non-ordinals don't work together 2337
-
25.3.5 - 2025-08-14
- fix: Ordinals and non-ordinals don't work together 2337
-
25.3.4 - 2025-08-10
-
25.3.3 - 2025-08-10
-
25.3.2 - 2025-07-09
from i18next GitHub release notesfeat:
exists()method now respectsreturnObjectsoption - returnsfalsewhen accessing an object key withreturnObjects: false, enabling detection of object vs string keys 2359Note: This is a potential behavior change. If you were previously calling
exists()withreturnObjects: falseon object keys, those calls will now returnfalseinstead oftrue. This enables developers to detect whether a key points to an object or string value.enableSelector: truein your configuration optionsenableSelector: "optimize", i18next can now handle translation dictionaries of any size, without affecting IDE performance or build timesImportant
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: