Sourced from i18next-browser-languagedetector's changelog.
8.2.2
- fix: the path and hash detectors keep digits in a language segment, so
/es-419/and#/es-419are detected ases-419instead ofes-(which i18next resolved toes). Segments that start with a digit (/2024/) still yield no language, andlookupFromPathIndex/lookupFromHashIndexpoint at the same segments as before. Thanks@nk-batman21327
6e4fa01
8.2.2e66a3af
releasefeedf66
fix: keep digits of region subtags in path and hash detection (#327)a05f0c5
Bump brace-expansion from 1.1.18 to 1.1.21 (#326)ca2366c
Bump js-yaml (#325)b1edea5
Bump browserslist from 4.28.2 to 4.28.9 (#324)b4b823e
docs: "For AI assistants" paragraph in the README8d55454
chore: keep dev-only and local files out of the npm packagefa858b6
Bump brace-expansion from 1.1.14 to 1.1.18 (#323)4515f87
Bump @babel/core from 7.29.0 to 7.29.6 (#321)