Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

chore(deps): update dependency ng-packagr to v15 #185

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 21, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ng-packagr 14.2.2 -> 15.2.2 age adoption passing confidence

Release Notes

ng-packagr/ng-packagr

v15.2.2

Compare Source

Bug Fixes
  • always set destination directory (4e49d12)

v15.2.1

Compare Source

v15.2.0

Compare Source

Bug Fixes
15.1.2 (2023-02-09)
Bug Fixes
15.1.1 (2023-01-12)
Performance
  • create a single stylesheet renderer worker instance (6718f6e), closes #​2530

v15.1.2

Compare Source

v15.1.1

Compare Source

v15.1.0

Compare Source

Features
Performance
  • move stylesheet processing into a worker pool (9eaa398)
Bug Fixes
  • include cssUrl and styleIncludePaths in the CSS cache key (6bb7a4a), closes #​2523

v15.0.3

Compare Source

v15.0.2

Compare Source

v15.0.1

Compare Source

v15.0.0

Compare Source

⚠ BREAKING CHANGES
  • ng-packagr no longer supports Node.js versions 14.[15-19].x and 16.[10-12].x. Current supported versions of Node.js are 14.20.x, 16.13.x and 18.10.x.
  • TypeScript versions older than 4.8.2 are no longer supported.
  • Deprecated support for Stylus has been removed. The Stylus package has never reached a stable version and it's usage in the ng-packagr is minimal. It's recommended to migrate to another CSS preprocessor that the ng-packagr supports.
Features
  • add support for tailwindcss (fdc0707), closes #​1943
  • add support for Node.js version 18 (e70e3a3)
  • drop support for TypeScript 4.6 and 4.7 (56d9a85)
  • switch to sass modern API (b1ebee3)
Bug Fixes
  • grammatical update error message (6d7d2a9)
  • remove support for Stylus (2f92ab8)
  • emit TypeScript declaration diagnostics (844ea6c), closes #​2405
  • exclude scanning node_modules when trying to locate README.md (b54159b), closes #​2418
  • exclude scanning nested node_modules when locating README.md (4e4c00b), closes #​2459
  • show actionable error when component resource is not found (5dcba25)

v14.3.0

Compare Source


Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 4am every weekday,every weekend" in timezone Asia/Kolkata, 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 has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Contributor Author

renovate bot commented Dec 21, 2022

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: @angular/[email protected]
npm ERR! node_modules/@angular/compiler-cli
npm ERR!   dev @angular/compiler-cli@"14.2.12" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @angular/compiler-cli@"^15.0.0 || ^15.2.0-next.0" from [email protected]
npm ERR! node_modules/ng-packagr
npm ERR!   dev ng-packagr@"15.2.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-03-21T20_38_30_319Z-debug-0.log

@renovate renovate bot force-pushed the renovate/ng-packagr-15.x branch 4 times, most recently from be025d5 to 306a82c Compare January 14, 2023 08:33
@renovate renovate bot force-pushed the renovate/ng-packagr-15.x branch 4 times, most recently from 95efc5d to ef1fc33 Compare February 14, 2023 06:16
@renovate renovate bot force-pushed the renovate/ng-packagr-15.x branch from ef1fc33 to 10e6f25 Compare February 22, 2023 12:49
@renovate renovate bot force-pushed the renovate/ng-packagr-15.x branch from 10e6f25 to 84ac573 Compare March 10, 2023 21:54
@renovate renovate bot force-pushed the renovate/ng-packagr-15.x branch from 84ac573 to a492e7c Compare March 20, 2023 21:46
@renovate renovate bot force-pushed the renovate/ng-packagr-15.x branch from a492e7c to 7101381 Compare March 21, 2023 20:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants