Skip to content

chore(deps): update dependency ng-packagr to v20 #109

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 28, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ng-packagr ^19.1.0 -> ^20.0.0 age adoption passing confidence

Release Notes

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

v20.0.0

Compare Source

⚠ BREAKING CHANGES
  • Node.js versions from 22.0 to 22.10 are no longer supported
  • Node.js v18 is no longer supported
  • TypeScript versions less than 5.8 are no longer supported.
Features
  • expand browser support to widely available Baseline (94f7fbe)
  • add DTS bundles for entry-points (ca9d568), closes #​139
  • support Angular version 20 (cebe060)
  • drop support for TypeScript older than 5.8 (a8255ce)
  • support Sass package importers (f767d3c)
Bug Fixes
  • correctly resolve SCSS resources from nested paths (f34a73d), closes #​3006
  • correctly update reference to bin (e73db8e), closes #​3062
  • update min Node.js support to 20.19, 22.12, and 24.0 (5a7eac4)
  • ensure in package .browserslistrc is correctly resolved (14ed50d)
  • prevent nested CSS in components (e2d9ef0)
  • disable TypeScript composite option with Angular compiler (5dfbdba)
  • disable emitting empty chunk warning (638c107)
  • remove Node.js v18 support (69d9d9e)
  • update minimum supported Node.js 22 version to 22.11.0 (a836a71)
Performance
  • optimize node deletion using Set (a99785c)
  • prevent redundant entry-point builds in watch mode (2f2668b), closes #​2936

v19.2.2

Compare Source

Bug Fixes
  • correctly handle undefined stylesheet processor (4598b67), closes #​3005

v19.2.1

Compare Source

Bug Fixes
  • correctly resolve SCSS resources from nested paths (2fcbe68), closes #​3006

v19.2.0

Compare Source

v19.1.2

Compare Source

  • add tailwindcss version 4 as a valid peer dependency (719577c)

v19.1.1

Compare Source


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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.

Copy link
Contributor Author

renovate bot commented May 28, 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: [email protected]
npm error Found: @angular/[email protected]
npm error node_modules/@angular/compiler-cli
npm error   dev @angular/compiler-cli@"^19.1.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @angular/compiler-cli@"^20.0.0 || ^20.0.0-next.0 || ^20.1.0-next.0" from [email protected]
npm error node_modules/ng-packagr
npm error   dev ng-packagr@"^20.0.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/2025-05-28T13_25_49_658Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-28T13_25_49_658Z-debug-0.log

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