Update GroupDocs.Total-Angular

GroupDocs.Total App Product Family
1

I noticed that the repository is still on Angular 8, yet the README suggests installing @angular/cli@14.2.13.

Could this indicate a synchronization issue for the repo, or am I referring to the wrong project?
Repository: https://github.com/groupdocs-total/GroupDocs.Total-Angular

Thanks,
John

2

@john.mcqueide

Summary
You are likely seeing a mismatch because the README was updated for a future Angular 14 migration, while the code in the default branch is still on Angular 8. This kind of out‑of‑date documentation is common in open‑source projects that are in the middle of a version upgrade.

Why it happens

  • The actual Angular version a project can be built with is defined in its package.json (e.g., "@angular/core": "8.x.x") and the corresponding angular.json configuration. If those files list Angular 8, the project will only compile with an Angular 8‑compatible CLI, even if the README mentions a newer CLI.
  • Maintainers sometimes update the README to reflect an upcoming migration before the codebase is fully migrated, leading to the discrepancy you observed.
  • Without direct evidence from the repository (the retrieved snippets did not contain the relevant package.json or angular.json), we cannot confirm the exact versions present, but the pattern described above matches typical scenarios.

What to do next

  1. Check the declared Angular version
git clone
cd GroupDocs.Total-Angular
cat package.json | grep "@angular/"
cat angular.json | head -n 20

Look for entries such as "@angular/core": "8.x.x". The version numbers will tell you which Angular major version the code targets.

  1. Try building with the two CLI versions
  • Angular 8 CLI:
npm install -g @angular/cli@8
npm install
ng build
  • Angular 14 CLI (as the README suggests):
npm install -g @angular/cli@14.2.13
npm install
ng build

The build that succeeds without errors indicates the compatible CLI version.

  1. Inspect recent commits or branches
  • Browse the Commits and Branches tabs on GitHub for any mention of an Angular 14 upgrade or a branch named angular-14/upgrade-angular. If such a branch exists, the README may be describing that branch rather than the default main.
  1. Search the issue tracker
  • In the Issues section, search for keywords like angular, cli, version, or README. If the mismatch has already been reported, you’ll find a maintainer’s response. If not, consider opening a new issue to ask for clarification.
  1. Temporary workaround
  • Until the repository is confirmed to target Angular 14, use the CLI version that matches the Angular packages you discovered (most likely Angular 8). When the maintainers finish the migration, you can switch to the newer CLI as described in the updated README.

Note: The evidence retrieved by the system did not contain the package.json or angular.json from the GroupDocs.Total‑Angular repository, so the above reasoning is based on typical project structures and the observed README‑code version mismatch, not on direct file content.

:warning: I could not fully verify this explanation against the retrieved sources. Please double-check the behaviour in your environment and confirm the exact SDK/version.