feat: support i18next v22 type augmentation

[belgattitude]

Change example to support the new i18next v22 types augmentation.

To update look at https://github.com/i18next/next-i18next/pull/1997/files#diff-53f0261e2e3a0e94c11e361fb2729a6d2995921dca99da95aa77209f66226156

[belgattitude]

Issue

Type checks are lost when reworking the types from 'react-i18next.d.ts' to 'i18next.d.ts'

[belgattitude]

I'll debug tomorrow, but any help appreciated

links to keep an eye on (by @adrai)

• [TypeScript] Add default value for TDefaultResult i18next#1853 (comment) (merged in 22.0.2)

Ideally I'd like to provide a specific test for types

[adrai]

@pedrodurek any chance to help @belgattitude with this?

[pedrodurek]

Sorry guys, It's been a tough week. I'll have some time tomorrow to look into it.

[pedrodurek]

Hey @belgattitude, that's happening because next-i18next@12.1.0 is relying on the old react-i18next and 18next versions. https://github.com/i18next/next-i18next/blob/v12.1.0/package.json#L132-L134
cc: @adrai

[adrai]

Hey @belgattitude, that's happening because next-i18next@12.1.0 is relying on the old react-i18next and 18next versions. https://github.com/i18next/next-i18next/blob/v12.1.0/package.json#L132-L134

cc: @adrai

12.1 is the npm released version, but on master everything is up-to-date @pedrodurek

[pedrodurek]

Once we create a new version for next-i18next based on master, the types will work. Alternatively, we can add npm override for next-18next

"overrides": {
  "next-i18next": {
    "react-i18next": "12.0.0",
    "i18next": "22.0.3"
  }
}

[adrai]

Once we create a new version for next-i18next based master, the types will work. Alternatively, we can add npm override for next-18next

"overrides": {
  "next-i18next": {
    "react-i18next": "12.0.0",
    "i18next": "22.0.3"
  }
}

@belgattitude can you check that overrides?

[adrai]

@belgattitude as soon as you think we're ready for releasing, let me know... probably still waiting for this #1998 ?

[belgattitude]

Cool, gonna check tomorrow. Make sense

[pedrodurek]

[socket-security]

Socket Security Pull Request Report

Dependency issues detected. If you merge this pull request, you will not be alerted to the instances of these issues again.

😵‍💫 Bin script confusion

This package has multiple bin scripts with the same name. This can cause non-deterministic behavior when installing or could be a sign of a supply chain attack

Consider removing one of the conflicting packages. Packages should only export bin scripts with their name

Package	Bin script	Location
jest@26.6.3 (added)	jest	package.json
jest-cli@26.6.3 (added)	jest	package.json via jest@26.6.3

Pull request report summary

Issue	Status
Install scripts	✅ 0 issues
Native code	✅ 0 issues
Bin script confusion	⚠️ 2 issues
Bin script shell injection	✅ 0 issues
Unresolved require	✅ 0 issues
Invalid package.json	✅ 0 issues
HTTP dependency	✅ 0 issues
Git dependency	✅ 0 issues
Non-existent author	✅ 0 issues
Potential typo squat	✅ 0 issues
Known Malware	✅ 0 issues
Telemetry	✅ 0 issues
Protestware/Troll package	✅ 0 issues

Bot Commands

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@2.4.2

• @SocketSecurity ignore jest@26.6.3
• @SocketSecurity ignore jest-cli@26.6.3

Powered by socket.dev

[belgattitude]

Works like a charm 👍

as soon as you think we're ready for releasing, let me know... probably still waiting for this #1998 ?

@adrai regarding #1998, I'd like to have an hour tomorrow to test typescript 4.9-rc before merging.

[pedrodurek]

Looks great to me!