Since 8.9.0, parsing is ignoring files outside the configuration file folder. about i18next-parser HOT 9 OPEN

We've also run into this at Ghost - the commit above is the revert back to v8.8.0

from i18next-parser.

@karellm Is this issue a bug, or an intentional breaking change? We've had to pause all updates to i18next-parser due to this

from i18next-parser.

Such a problem also appeared. Any progress?

from i18next-parser.

Also bumped into this issue.

from i18next-parser.

Same issue. I had to downgrade to 8.8.0
Is there a breaking tweak to config necessary? Changelog did not mention anything.

from i18next-parser.

To follow up, I use a monorepo.
This is what my i18next-parser.config.js looks like

module.exports = {
  contextSeparator: '_',
  createOldCatalogs: false,
  defaultNamespace: 'translation',
  defaultValue: (locale, namespace, key) => {
    if (locale === 'en-US') {
      return key;
    }
    return '__NOT_TRANSLATED__';
  },
  indentation: 2,
  keepRemoved: false
  keySeparator: false,
  lexers: {
    js: ['JavascriptLexer'],
    ts: ['JavascriptLexer'],
    jsx: ['JsxLexer'],
    tsx: ['JsxLexer'],
    default: ['JavascriptLexer'],
  },
  lineEnding: 'auto',
  locales: ['en-US', 'nl-NL'],
  namespaceSeparator: false,
  output: '../../locales/$LOCALE.json',
  pluralSeparator: '____',
  input: '../*/src/**/*.{js,ts,jsx,tsx}',
  sort: false,
  skipDefaultValues: false,
  useKeysAsDefaultValue: false,
  verbose: false,
  failOnWarnings: false,
  customValueTemplate: null,
};

from i18next-parser.

It's not intentional but have limited time to look at it currently. If someone can open a PR that would be greatly appreciated.

from i18next-parser.

This seems to be working again in 8.13.0
@giovannetti-eric I would give this another go

from i18next-parser.