Support multiple apps/libs in NX workspace

I’m submitting a…

[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior

At the moment it is only possible to set one app within the rootTranslationsPath. I am using NX with multiple apps and libs.

Expected behavior

It should be possible to have multiple root translation paths / to support multiple apps.

Minimal reproduction of the problem with instructions

Create two projects within a NX workspace.

What is the motivation / use case for changing the behavior?

Make it usable within NX.

[adgoncal]

It would also be nice to have support for --project and check angular.json for the given project. For example:

// package.json
{
  "scripts": {
    "transloco:extract": "transloco-keys-manager extract"
  }
}

// angular.json
{
 "projects": {
    "first-app": {
      "sourceRoot": "apps/first-app/src"
    }
  }
}

// transloco.config.ts
module.exports = {
  translationPath: 'assets/i18n'
};

Then

npm run transloco:extract -- --project first-app

would use apps/first-app/src/assets/i18n as the rootTranslationPath.

---

Furthermore (optional), if --project was the default arg, then we would be able to use

npm run transloco:extract -- first-app

Similar to how we can run tests for a given project using

ng test first-app

[adgoncal]

@adgoncal Thanks again for the feedback, can you try 1.3.2? 🙂

@shaharkazaz That is perfect! Thank you again!