Suggestion: Bringing `ngx-translate-extract` under the `ngx-translate` workspace

[pmpak]

Hello @CodeAndWeb , I'm reaching out regarding ngx-translate-extract, which is commonly used alongside @ngx-translate for extracting translation keys. (It is like the ng extract-i18n equivalent for @ngx-translate).

This library has come a along way through different maintainers and forks after the original author was unable to continue to maintain it with the most up-to-date fork currently being from vendure-ecommerce/ngx-translate-extract.

Unfortunately, the current maintainer also appears unable to continue to maintain it, since PRs for bugfixes have been standing open for a long time, including the latest which adds support for Angular 20.

Since I believe this tool is essential for many @ngx-translate users, I'd like to propose bringing ngx-translate-extract under @ngx-translate. While I could maintain a separate fork, I would prefer to not create yet another fork of this library. I believe it complements and fits well within @ngx-translate workspace.

I'm happy to maintain the project by at least keeping it up to date with the Angular updates.

Let me know your thoughts.

[CodeAndWeb]

I absolutely see your point... I am just currently struggling to find the time to work on ngx-translate itself.
Adding more in top of it won't make it much better...

[pmpak]

Hello @CodeAndWeb, I totally understand the situation and really appreciate your work on @ngx-translate.

To clarify, my intention wasn't to add extra work, only to bring ngx-translate-extract under ngx-translate as a separate repository (The title might be a bit misleading, I meant org not workspace), and I am happy to maintain it.

Of course, if this still adds overhead for the org right now, I totally understand that and will explore other options, or hopefully the vendure-ecommerce/ngx-translate-extract maintainer may find time to review open PRs. Just wanted to offer, as I think it would be a sustainable way to keep the CLI alive and close to the library.

[rbalet]

If we have the go from @CodeAndWeb, @pmpak you can always do a PR and I'll review it and prepare it for a proper merge.

@pmpak But if ok, I would wait the 16.2.0 as the lib is a bit "unstable" due to the fair amount of changes we're doing

[pmpak]

Hello @rbalet

Thank you very much for your reply. There are two ways we can proceed (assuming we get the go and it is possible).

1. Fork the library into a new repository under @ngx-translate. This way the library remains isolated with its own release schedule. We can always discuss to align the major version numbers to keep the core and extract consistent.

2. Move the library into the @ngx-translate/core workspace. This way the library becomes a project within the monorepo, that will require some extra work because it is a plain TypeScript CLI library, and will need some tweaking to work properly (build/test/lint) within an Angular workspace. It is not a big deal, I maintain monorepos like that and it works fine, it will just require some extra effort to adapt it for the workspace.

Let me know which option you think would work best for you. I'm happy to help with either approach.