Add support for i18next v24

[lazka]

v24 no longer supports compatibilityJSON=v3 so skip the tests for it when running with i18next v24.

Fixes #1090

Why am I submitting this PR

See title

Does it fix an existing ticket?

Yes #1090

Checklist

• only relevant code is changed (make a diff before you submit the PR)
• tests are included and pass: yarn test (see details here)
• documentation is changed or added

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	566 kB	adrai, jamuhl

🚮 Removed packages: npm/[email protected]

View full report↗︎

[ripecosta]

Would it make sense to stop supporting v23 entirely instead?
If so, since that would be a breaking change, would it make sense to also move i18next to a peerDependency? It would help upstream projects with their dependency management.

[lazka]

Would it make sense to stop supporting v23 entirely instead?

Your call. I seemed easy enough to support both, and it would make my life easier as I have various packages using i18next that depend on this, so I could update things gradually. But I'd be happy to change things if wanted.

If so, since that would be a breaking change, would it make sense to also move i18next to a peerDependency? It would help upstream projects with their dependency management.

I don't quite understand how peerDependency could help as I've never worked with that. Note that i18next-parser is importing/using i18next directly (

i18next-parser/src/transform.js

Line 69 in 69a25da

this.i18next = i18next.createInstance()

) and is not plugin as noted here: https://docs.npmjs.com/cli/v10/configuring-npm/package-json#peerdependencies but maybe I'm missing something.