i18next parser

[delphiactual]

switch from i18next-scanner as it is no longer being maintained and has been silently failing in workflows.

while most of our functionality is retained, some caveats:

i18n.json is technically no longer used... not sure how i feel about that
dynamicKeys are populated via regex in the config file, I am sure someone here can make something much more graceful than my hamfisted attempt, but all our keys came thru.

EDIT: we can still use i18n.json by having pnpm i18n copy i18n.json over en.json before running i18next-parser

[bhollis]

Yeah I'd looked into this, but at least as of pretty recently I was seeing the pnpm i18n task working: I could add or remove keys from i18n.json and they'd get reflected in en.json. I'll have to test when I'm around my personal computer but I am not sure exactly what isn't working now.

I had my own i18next-parser branch but never got it working to my liking.

[bhollis]

BTW just confirmed that the existing i18n-scanner appears to work locally. Not saying we shouldn't switch but it's not broken afaik

[delphiactual]

it is silently failing in workflows...

https://github.com/DestinyItemManager/DIM/actions/runs/16492679800/job/46630963716

[delphiactual]

@bhollis what version of node are you running locally?

[bhollis]

I'm using the version specified in our .nvmrc

[delphiactual]

The nvmrc only specifies 22, the latest 22 from node.js is 22.17.1, which is what is being downloaded by the github workflow, it was also only released last week.

[bhollis]

Yeah I'm on v22.17.1