We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The --config option of the command line interface doesn't accept module JS files (those using import and export).
--config
import
export
My whole project is written as modules and I have the impression the whole JS ecosystem is moving toward using them.
We could have a configuration file i18next-scanner.js such as:
i18next-scanner.js
import { defaultNS, fallbackLng } from "./src/i18n/globals.cjs"; import fs from "node:fs"; const scannerConfig = { input: [ "src/app/**/*.{js,jsx}", ], defaultNs: defaultNS, ... }; export default scannerConfig;
and use it like this:
$ i18next-scanner --config i18next-scanner.js
The text was updated successfully, but these errors were encountered:
A PR was opened to do just that a long time ago: #155. It was closed without explanation though.
Sorry, something went wrong.
No branches or pull requests
🚀 Feature Proposal
The
--config
option of the command line interface doesn't accept module JS files (those usingimport
andexport
).Motivation
My whole project is written as modules and I have the impression the whole JS ecosystem is moving toward using them.
Example
We could have a configuration file
i18next-scanner.js
such as:and use it like this:
The text was updated successfully, but these errors were encountered: