Invalid i18n configuration: Locales 'ru' and 'en' cannot have the same subPath: ''.

[zip-fa]

Command

build

Is this a regression?

• Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Hey.
With v19.1 it's not possible to build with this config:

"sourceLocale": {
      "code": "ru",
      "subPath": ""
    },
    "locales": {
      "en": {
        "translation": "apps/frontend/src/locale/messages.en.xlf",
        "subPath": ""
      }
    },
"configurations": {
        "production-en": {
          "localize": ["en"]
        },
        "production": {
          "localize": ["ru"],
}

How about moving non-unique subPath check inside build configuration, but not global?

This should fail:

"configurations": {
 "production": {
          "localize": ["ru", "en"],
}
}

This should not:

"configurations": {
 "production": {
          "localize": ["ru"],
}
}

Minimal Reproduction

ng build

Exception or Error

Your Environment

v19.1

Anything else relevant?

No response

[burner-account]

I personally used baseHref="" for i18n versions of my app that each will be deployed to the / of their own subdomain.

I failed to get this to work with "subPath", is there a documented new way on how to have different languages on a different root paths?

[zip-fa]

You can make separate angular.json files and rename them before build in your CI, but let's wait for the official response

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}