Problem with build library package

[Obliczeniowo]

Which @angular/* package(s) are the source of the bug?

Don't known / other

Is this a regression?

No

Description

I have problem with build my library made in angular 12 and upgrade to angular 13

I know this is related to package.json: file of sub package:

{
  "ngPackage": {
    "lib": {
      "entryFile": "public-api.ts",
      "umdModuleIds": {
        "@angular/common": "@angular/common",
        "@angular/core": "@angular/core"
      }
    }
  },
  "dependencies": {
    "tslib": "^2.0.0"
  }
}

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

Configuration doesn't match the required schema.
Data path "/lib" must NOT have additional properties (umdModuleIds).

### Please provide the environment you discovered this bug in

```true
Angular cli 13

Anything else?

No response

[petebacondarwin]

This sounds like a problem with how ng-packagr has been configured.

[petebacondarwin]

In fact I think the problem you have is that in v13 we no longer generate UMD bundles so the umdModuleIds property is no longer valid. See https://github.com/ng-packagr/ng-packagr/blob/f7f1d0232780b531fc48631ff78d8d030d5501d5/CHANGELOG.md#1300-2021-11-03

[clydin]

As noted above, the umdModuleIds is not a valid option when using v13 as UMD files are no longer generated during builds. The update process should have executed a migration to removed the option. Was the project updated to v13 via the ng update command?

[alan-agius4]

The migration doesn’t handle ng-packagr configurations in package.json.

We should fix this and we should also deprecate such configurations. The package.json isn’t the right place to configure tools.

[Obliczeniowo]

hm I try solution like:

{
  "entryFile": "public-api.ts",
  "perDependences": {
    "@angular/common": "@angular/common",
    "@angular/core": "@angular/core"
  },
  "dependencies": {
    "tslib": "^2.0.0"
  }
}

but then it's build in incorrect way

Can you point me how correctly update library with multiple entry points?

[Obliczeniowo]

As noted above, the umdModuleIds is not a valid option when using v13 as UMD files are no longer generated during builds. The update process should have executed a migration to removed the option. Was the project updated to v13 via the ng update command?

I use:

npx @angular/cli@13 update @angular/core@13 @angular/cli@13

[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.}