Bug: transloco-keys-manager 6 does not extract keys from template with Angular 17

[ippeiukai]

Is there an existing issue for this?

• I have searched the existing issues

Is this a regression?

Yes

Current behavior

I'm trying out transloco with my Angular 17 project.
I found out transloco-keys-manager 6.0.0 and 6.1.0 do not extract keys from template files that 5.1.0 does. No error, just no keys from the templates in the output pot.

Expected behavior

Either incompatibility is clearly documented, or the latest version of transloco-keys-manager works with Angular >=16 as transloco 7.x do.

Please provide a link to a minimal reproduction of the bug

sorry, it's private repo

Transloco Config

No response

Debug Logs

No response

Please provide the environment you discovered this bug in

Transloco: 7.5.1
Transloco Keys Manager: 6.1.0
Angular: 17.3.11
Node: 18.20.3
Package Manager: npm 10.7.0
OS: macOS 14.7.2

Additional context

With following override in package.json, the keys are extracted successfully with 6.1.0:

  "overrides": {
    "@jsverse/transloco-keys-manager": {
      "@angular/compiler": "17.3.11"
    }
  }

I would like to make a pull request for this bug

No

[shaharkazaz]

@ippeiukai Can you share a small reproduction of the cases not being extracted?

[ippeiukai]

@shaharkazaz I'll have to find a spare time for that.

FYI During debugging, the template file was reduced to following and still had issue:

<ng-container *transloco="let t">
  <!-- t(closing) -->
  <div>{{ t('close') }}</div>
</ng-container>

"closing" gets extracted but not "close".

[shaharkazaz]

Thanks, I'll try to take a look.
All the specs are passing so that's surprising.

A full reproduction will be better but I'll try to work with that 👍

[emzet]

@shaharkazaz same issue for me with v6, when downgrading to v5 extract command works also for .html files

[emzet]

After updating Angular to v19 and transloco keys manager to v6, it resolves the issue, so the extract command works also for .html files