You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by ivanhofer October 2, 2021
This option only makes sense inside the rollup-process, so it should only be available there.
Currently the rollup- and webpack-process allows to configure the generator by passing it as an argument. This option should be removed and the config should always be loaded from the .typesafe-i18n.json-file. This would mean a breaking change so a error-massage should point to a migration-guide.
The text was updated successfully, but these errors were encountered:
The node-process is the recommended way to run the generator.
The rollup-plugin can be used to apply compile-time optimizations.
As of right now the webpack-plugin has no advantages. It can be used to start the generator when webpack is started.
Both plugins don't take generator-config options anymore,
Migrating is easy: just create a .typesafe-i18n,json in the root of your project and specify the options in that file.
Originally posted by ivanhofer October 2, 2021
This option only makes sense inside the rollup-process, so it should only be available there.
Currently the rollup- and webpack-process allows to configure the generator by passing it as an argument. This option should be removed and the config should always be loaded from the
.typesafe-i18n.json
-file. This would mean a breaking change so a error-massage should point to a migration-guide.The text was updated successfully, but these errors were encountered: