Open justinhippo opened 3 months ago
Have same issue :(
npm i -D 'glob-stream@<8.0.1’ fix this problem for me
Having the same issue, but yeah it appears a security fix update to the glob-stream package broke this.
I spend over hour debugging, and ended up installing i18next-parser
in version 7.9.0
Same issue here. Downgrade resolved it.
FYI - glob-stream 8.0.2 fixes this. If you're using yarn, you can update it with yarn up glob-stream --recursive
. I'm not sure how to update transitive dependencies with other package managers...
🐛 Bug Report
After freshly installing
i18next-parser
withnpm i -g i18next-parser
and setting up a configuration file, running the CLI givesTo Reproduce
A minimal reproducible example. A codesandbox example or similar or at least steps to reproduce the behavior:
i18next-parser.config.js
Expected behavior
i18next-parser
runsYour Environment