The support for i18n has not survived the conversion to typescript.
The boilerplate docs state that we should npm run extract-intl or npm run generate language, however these scripts require the i18n.js file to continue to use require and not ESModule syntax. i18n.js lives in out app directory, now as i118n.ts, and is imported into many esmodule files using esmodule syntax on both sides, we need to look at how we can break this relationship up to maintain the integrity of our app in typescript and the functionality of our scripts.
The support for i18n has not survived the conversion to typescript.
The boilerplate docs state that we should
npm run extract-intlornpm run generate language, however these scripts require the i18n.js file to continue to use require and not ESModule syntax. i18n.js lives in out app directory, now as i118n.ts, and is imported into many esmodule files using esmodule syntax on both sides, we need to look at how we can break this relationship up to maintain the integrity of our app in typescript and the functionality of our scripts.