carloscuesta / carloscuesta/gitmoji-cli
Support Multiple Configuration File Formats (JS, MJS, CJS, TS)
- Dominant language
- JavaScript
- Stars
- 4.8k
- Forks
- 212
- PR merge metrics
- No merged PRs in 30d
Description
### Description of the problem
Currently, Gitmoji CLI only supports a single configuration file format: gitmoji-rc.json.
This limits flexibility for projects that could benefit from dynamic or typed configurations.
Supporting multiple file formats (including JavaScript and TypeScript) would allow configuration logic to be centralized and reused across tools.
### Solution
Enable Gitmoji CLI to support additional configuration formats:
- gitmoji.config.js
- gitmoji.config.ts
- maybe others ...
### Alternatives
_No response_
### Additional context
_No response_
### Validations
- [x] Follow our [Code of Conduct](https://github.com/carloscuesta/gitmoji-cli/blob/master/CODE_OF_CONDUCT.md)
- [x] Read the [Contributing Guide](https://github.com/carloscuesta/gitmoji-cli/blob/master/.github/CONTRIBUTING.md).
- [x] Check that there isn't already an issue requesting the same feature.
Contributor guide
Research direction
Start by locating where Gitmoji CLI currently discovers and loads gitmoji-rc.json. Determine how JavaScript and TypeScript configuration files would be selected and loaded, then define supported formats and behavior for each. Done means the CLI accepts the requested configuration formats without breaking the existing JSON format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100