feat: add meta with codes on warnings to allow conditional logging

[delta-9]

Checklist

• only relevant code is changed (make a diff before you submit the PR)
• run tests npm run test
• tests are included
• commit message and code follows the Developer's Certification of Origin

Checklist (for documentation change)

• only relevant documentation part is changed (make a diff before you submit the PR)
• motivation/reason is provided
• commit message and code follows the Developer's Certification of Origin

[adrai]

not necessary, since you can now inject your own logger: i18next/react-i18next-gitbook#150 (comment)

[delta-9]

@adrai I saw your changes just now, cool!, this PR now just adds meta so I can filter what to log or not

[adrai]

I suggest, you move this logic out to your custom logger... else this will bloat the code size even more... //cc @VIKTORVAV99

[delta-9]

I suggest, you move this logic out to your custom logger... else this will bloat the code size even more... //cc @VIKTORVAV99

fair enough, I reworked the changes to includes only what is needed to do that from the logger

[adrai]

Do you really need extra error codes? The whole i18next core code base has no error codes...

[coveralls]

coverage: 95.797% (-0.6%) from 96.386%
when pulling 4be7a37 on delta-9:feat-add-option-to-override-warn-logger
into ff509ba on i18next:master.

[delta-9]

Do you really need extra error codes? The whole i18next core code base has no error codes...

the error codes is to be able to identify the warnings in the code.
it also adds the i18nkey to the warning logged so its easier to find the culprit trans.

the i18nkey also allow to add a logic to warnOnce per key in the custom logger, now it warn on each renders.

for the code I could do some string regexp on the messages to figure out the cause of the error,
and for the i18nkey, Its also possible to debug following the stack trace and put some trace until I find the right call.

[VIKTORVAV99]

Maybe there are benefits from this but I would like you to consider two things:

First this will increase the overhead and bundle size for all users of i18next, I've been trying to push this bundle down as it's one of the bigger parts of our app we can't change at the moment.

Secondly it feels like this is just duplicating the error message. If we do this I would switch to something what react does and only log the error codes with a link to look up what they mean. But that requires other changes as well.

That is just my thought on the matter though but I would really like to avoid duplicating any information or functionality for the sake of making it a little more convenient for one project or developer.

[rawpixel-vincent]

I replaced the error map with a tuple, and reduced duplicates, it's adding 201 bytes to react-i18next.min.js build compared to current master

moving the error messages to the documentation might be a good idea. They can be better explained in the docs, and changed without worrying of breaking someone code.

[delta-9]

If you ask me, I think it's needed for sanity. But the code can run without it and the type can be removed to accept any string as code.

[delta-9]

good news @adrai I moved the error code to a type declaration file so its not in the code.

the minify js is now 20 bytes less than master 🎉

[delta-9]

added types for the warning args along an example of usage in the logger plugin

edit: typo in example

[adrai]

TS tests seems to fail: https://github.com/i18next/react-i18next/actions/runs/12542746999/job/34976361013?pr=1826

[delta-9]

it should be fixed, but I can't make the test fail locally, npm run test pass

[adrai]

it's included in v15.4.0