i18n export doesn't export scopes from js files?

[JohnRDOrazio]

I defined a translation scope in a stimulus controller, which is not defined in any erb files, only in the stimulus controller.

When I run i18n lint:scripts, this translation scope is correctly picked up as missing:

   - app/javascript/controllers/home_controller.js:12:21: en.pages.home.helloWorldFrom
   - app/javascript/controllers/home_controller.js:12:21: es.pages.home.helloWorldFrom
   - app/javascript/controllers/home_controller.js:12:21: it.pages.home.helloWorldFrom

However, when I run i18n export, the same scope is not exported to my translations.json file.

With the previous version 3 of i18n-js, I would run bundle exec rails i18n:js:export, which would correctly export all translation scopes from javascript files.

EDIT: this actually is not correct, bundle exec rails i18n:js:export would only transform the yml translation files into the relative js or json translation file; it was i18n-tasks add-missing itself that would pick up on translation strings in js files. Answer is now below.

I have a very basic i18n.yml config file:

translations:
  - file: "app/javascript/src/translations.json"
    patterns:
      - "*"

So I don't believe anything there is preventing the export. Should we still be using a middleware with i18n-js v4?

[JohnRDOrazio]

Actually I found the fix. Simply i18n-tasks missing or add-missing wasn't picking up on the translation strings because now we have lowercase i18n instead of I18n. The only way I could get it to work was to copy i18n to I18n:

import { i18n } from "../config/i18n"
const I18n = i18n;

Then I use I18n.t('scope.string') instead of i18n.t('scope.string') . And now i18n-tasks missing is picking up the missing strings in the js files.

Another way to possibly fix this would be to patch the i18n-tasks gem to accept a lowercase i18n when scanning, see the related discussion here: glebm/i18n-tasks#453

I also issued a PR on the i18n-js-examples repo to help clear this up: fnando/i18n-js-examples#1