ESM support + Easier way to specify translationKeyMatcher #31
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
New command --translation-key-matcher
This makes it easier to modify the matcher for more libraries like i18n-node, who use
![display](https://user-images.githubusercontent.com/2999487/204080855-7da530d2-10f5-4dc0-ac7f-d4d63b4ea5f8.png)
__
:ESM module configuration file
When creating the configuration file from inside an ES-Modules (esm) the parser is not able to read the Common-js module without the
.cjs
extension.To fix that we could use a .json configuration file without the support for callbacks or a .cjs file.
i18n-unused.config.json :
i18n-unused.config.cjs :
closes #30