Skip to content

Accept a JS module as value for --config #263

@DamienCassou

Description

@DamienCassou

🚀 Feature Proposal

The --config option of the command line interface doesn't accept module JS files (those using import and export).

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:

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions