jsverse / transloco-keys-manager

πŸ¦„ The Key to a Better Translation Experience

Home Page:https://github.com/jsverse/transloco/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Bug: transloco-keys-manager find cause terminal endless flood

kekel87 opened this issue Β· comments

Is there an existing issue for this?

  • I have searched the existing issues

Is this a regression?

No

Current behavior

When in launch transloco-keys-manager find in my project recently uupdate to angular 13.1.1 (from 13.0.2), it result of endless terminal flood with weird charactere.

It works correctly with Angular 13.0.2 !

image

Expected behavior

When in launch transloco-keys-manager find in angular 13.1.1 project, I expect regular ouput:

> transloco-keys-manager find
 πŸ•΅ πŸ”Ž  Starting Search For Missing Keys πŸ” πŸ•΅
√ Extracting Template and Component Keys πŸ—
√ Checking for missing keys ✨
√ Summary
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ File Name β”‚ Missing Keys β”‚ Extra Keys                                 β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€

Please provide a link to a minimal reproduction of the bug

no

Transloco Config

module.exports = {
  rootTranslationsPath: 'assets/i18n/',
  langs: ['en', 'fr'],
  keysManager: {
    unflat: true,
    sort: true,
  }
};

Debug Logs

No response

Please provide the environment you discovered this bug in

Transloco: 3.1.1
Transloco Keys Manager: 3.2.0
Angular: 13.1.1
Node: 14.17.0
Package Manager: NPM 6.14.13
OS: Windows 11

Additional context

No response

I would like to make a pull request for this bug

No

Ok, I just found it. It's related to "colors" and what's happening on Github.

I forced the version to 1.4.0.

We could update the dependency to cli-table3 to 0.6.1 to fix the issue.
See cli-table/cli-table3#251, they patched it.