search

i18next / i18next-parser

Parse your code to extract translation keys/values and manage your catalog files
MIT License
466 stars 189 forks source link

Can't extract translations from siblings folders #990

Open pybuche opened 4 months ago

pybuche commented 4 months ago

🐛 Bug Report

I'm currently working on a yarn workspace monorepo and I need to extract translations from two different workspace. I decided to create a new workspace called i18n so I setup the i18n object there, store the translations and define extraction scripts there. However it seems that the input configuration field doesn't look into siblings folders. For instance, with such a tree structure:

i18n/
├─ i18n.js
├─ i18next-parser-config.js
├─ package.json
app1/
├─ file.js
├─ package.json
app2/
├─ file.js
├─ package.json

And an i18next-parser-config.js being:

export default {
  defaultNamespace: "common",
  input: ["../**/*.js"],
  output: "locales/$LOCALE/$NAMESPACE.json"
}

It parsers files from i18n/, but not from app1/ or app2/

To Reproduce

I managed to create a minimal repository

Expected behavior

I'd expect the parser to browser folders where I'm asking it to do. Is there a way to do it with the current configuration? Am I missing something? Thanks!

Your Environment

TheBeeL commented 1 month ago

Seems like a duplicate of #939

Try using version 8.8.0