Skip to content

chore(deps): update dependency ng-packagr to v21#241

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/ng-packagr-21.x
Open

chore(deps): update dependency ng-packagr to v21#241
renovate[bot] wants to merge 1 commit intomainfrom
renovate/ng-packagr-21.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 4, 2025

This PR contains the following updates:

Package Change Age Confidence
ng-packagr 20.3.221.1.0 age confidence

Release Notes

ng-packagr/ng-packagr (ng-packagr)

v21.1.0

Compare Source

Features
  • add importAttributesKey: 'with' to Rollup output options (ba4f690), closes #​3212
Bug Fixes
  • correctly identify external modules (7c24c84)
21.0.1 (2025-12-15)
Bug Fixes
  • correctly identify external modules (e0f7b22)

v21.0.1

Compare Source

v21.0.0

Compare Source

⚠ BREAKING CHANGES
  • TypeScript versions older than 5.9 are no longer supported.
  • The javascriptEnabled option for Less is no longer supported. Projects relying on inline JavaScript within Less files will need to refactor their stylesheets to remove this dependency.
Bug Fixes
  • drop support for TypeScript 5.8 (7b48224)
  • remove deprecated javascriptEnabled option for Less (d57278d)
Features
  • write the types in types directory (7a5e8fb)
  • add support for Angular version 21 (ed70e23)

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 4, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @ngx-page-object-model/source@undefined
npm error Found: @angular/compiler-cli@20.3.9
npm error node_modules/@angular/compiler-cli
npm error   dev @angular/compiler-cli@"20.3.9" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/compiler-cli@"^21.0.0 || ^21.1.0-next" from ng-packagr@21.1.0
npm error node_modules/ng-packagr
npm error   dev ng-packagr@"21.1.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-02-02T19_11_10_468Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-02T19_11_10_468Z-debug-0.log

@renovate renovate bot force-pushed the renovate/ng-packagr-21.x branch 5 times, most recently from f618b6f to 7a5ee6b Compare December 5, 2025 02:35
@renovate renovate bot force-pushed the renovate/ng-packagr-21.x branch from 7a5ee6b to 4bd022c Compare December 15, 2025 17:27
@renovate renovate bot force-pushed the renovate/ng-packagr-21.x branch from 4bd022c to 27c30f7 Compare January 14, 2026 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants