Skip to content
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

chore(deps): update dependency ng-packagr to v19 #2091

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 19, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
ng-packagr 12.2.7 -> 19.0.1 age adoption passing confidence

Release Notes

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

v19.0.1

Compare Source

v19.0.0

Compare Source

Features
Bug Fixes

v18.2.1

Compare Source

18.2.1 (2024-08-21)

v18.2.0

Compare Source

v18.1.0

Compare Source

Features
  • add support for TypeScript 5.5 (ae2a698)

v18.0.0

Compare Source

⚠ BREAKING CHANGES
  • Node.js support for versions <18.19.1 and <20.11.1 has been removed.
Bug Fixes
  • incorrect path resolution for entry-points when generating FESM (f2cd914), closes #​2838
Features
  • add support for Angular 18 (9bef232)
  • add NgPackagrOptions to public api (ffc512e)
  • add support for polling (2c7f75b)
  • support TypeScript 5.4 (07d5cea)

v17.3.0

Compare Source

v17.2.1

Compare Source

v17.2.0

Compare Source

Features
Bug Fixes
  • support string as plugin option in custom postcss plugin config (bb67204)
  • handle absolute url reference in CSS files (3d96591)

v17.1.2

Compare Source

v17.1.1

Compare Source

v17.1.0

Compare Source

Bug Fixes
  • add missing tailwind @screen directive in matcher (ad1bd50)
  • remove direct imports to rollup (45336ae), closes #​2749
  • correctly validate secondary entry-points config (5ff4afd)
  • use rollup wasm version when rollup fails to load (1ed0dc9), closes #​2722
Performance
  • do not update package.json version on watch mode (1225a24)
  • embeed assets in css using esbuild instead of postcss (fe3e052)
  • only process component styles with postcss when needed (84cf578)
  • only emit changed DTS and JS from NG compiler (cd0f508)
  • only write FESM files when content changes during watch mode (fb096a0)
  • reduce TypeScript JSDoc parsing (8228740)

v17.0.3

Compare Source

Bug Fixes

v17.0.2

Compare Source

v17.0.1

Compare Source

Bug Fixes

v17.0.0

Compare Source

⚠ BREAKING CHANGES
  • TypeScript versions before 5.2 are no longer supported.
Features
  • esbuild can't resolve secondary entry point from library (29f417e)
  • drop support for TypeScript versions before 5.2 (72500c3)
  • add support for Angular 17 (cbb06ee)
  • support TypeScript 5.2 (0acd2c4)
Bug Fixes

v16.2.3

Compare Source

Bug Fixes

v16.2.2

Compare Source

v16.2.1

Compare Source

v16.2.0

Compare Source

v16.1.0

Compare Source

Features
  • support TypeScript 5.1 (fcc0c6a)
  • support incremental TypeScript semantic diagnostics (d3b9488)
Bug Fixes
16.0.1 (2023-05-10)
Bug Fixes
  • warn when finding conflicting package export conditions (b08b075), closes #​2609

v16.0.1

Compare Source

v16.0.0

Compare Source

⚠ BREAKING CHANGES
  • TypeScript 4.8 is no longer supported.

  • Several changes to the Angular Package Format (APF)

    • Removal of FESM2015
    • Replacing ES2020 with ES2022
    • Replacing FESM2020 with FESM2022
  • Node.js v14 support has been removed

    Node.js v14 is planned to be End-of-Life on 2023-04-30. Angular will stop supporting Node.js v14 in Angular v16. Angular v16 will continue to officially support Node.js versions v16 and v18.

  • NGCC integration has been removed and as a result Angular View Engine libraries will no longer work.

Features
  • (APF) Angular Package Format updates (4ae531c)
  • remove NGCC integration (d9fdc89)
Bug Fixes
  • always set destination directory (4e89bcf)
  • remove Node.js v14 support (a091d82)

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

v14.2.2

Compare Source

Bug Fixes
  • exclude scanning nested node_modules when locating README.md (3b74c0f), closes #​2459

v14.2.1

Compare Source

v14.2.0

Compare Source

Features
  • add support for TypeScript 4.8 (387a4e1)

v14.1.0

Compare Source

v14.0.4

Compare Source

v14.0.3

Compare Source

v14.0.2

Compare Source

14.0.2 (2022-06-10)

v14.0.1

Compare Source

No visible changes

v14.0.0

Compare Source

⚠ BREAKING CHANGES
  • Support for TypeScript 4.4 and 4.5 has been removed. Please update to TypeScript 4.6.
  • Support for Node.js v12 has been removed as it will become EOL on 2022-04-30. Please use Node.js v14.15 or later.
  • package.json is not longer a valid method to configure ng-packagr. Use ng-package.json instead.
Features
  • support TypeScript 4.7 (5574598)
  • remove handling of package.json as configuration (a94bd14), closes #​2176
  • update generated output to APF 14 (c6f6e4d)
  • support more complex assets configurations (6776e17), closes #​1497
  • drop support for Node.js 12 (181ac25)
  • support TypeScript 4.6.2 (9faef17)
Bug Fixes
  • watch mode when using ng-packagr CLI directly (0f8f92a)
  • join paths instead of resolving (0a54e7d), closes #​2241
  • avoid a recursive export when entryfile is named index.ts (4c96acb)
  • ignore circular dependency warnings (9b93a18)
  • remove hardcoded moduleResolution (3f5448d)
  • re-allow index.ts as entry-files (8c5cc4f)
  • invalid browsers version ranges (547a11f)

v13.3.1

Compare Source

Bug Fixes
  • watch mode when using ng-packagr CLI directly (c2338a1)

v13.3.0

Compare Source

Features
  • add support for TypeScript 4.6 (fe19978)

v13.2.1

Compare Source

Bug Fixes
  • invalid browsers version ranges (ccdc339)

v13.2.0

Compare Source

Bug Fixes
13.1.3 (2022-01-13)
Bug Fixes
  • update dependency postcss-preset-env to v7
13.1.2 (2021-12-15)
Bug Fixes
  • close rollup bundle after write (cf5de76)
13.1.1 (2021-12-08)

v13.1.3

Compare Source

v13.1.2

Compare Source

v13.1.1

Compare Source

v13.1.0

Compare Source

Features
  • add support for TypeScript 4.5 (b4d3f5c)
13.0.8 (2021-11-24)
Bug Fixes
  • correctly append sourceMappingUrl when saving FESMs into cache (657eacd), closes #​2172
13.0.7 (2021-11-23)
Bug Fixes
13.0.6 (2021-11-18)
Bug Fixes
13.0.5 (2021-11-17)
Bug Fixes
  • ~~remove files property from default tsconfig (c4cd3a7), closes #​2156~~
13.0.4 (2021-11-17)
Bug Fixes
  • --version doesn't work (ba835bb), closes #​2157
  • remove files property from default tsconfig (c4cd3a7), closes #​2156
  • show warning when configuring ng-packagr in package.json (037ccf5)
13.0.3 (2021-11-05)
Bug Fixes
  • handle multiple node_modules when resolving Sass (c7c51a3)
13.0.2 (2021-11-04)
Bug Fixes
13.0.1 (2021-11-04)
Bug Fixes
  • unable to add additional conditions to entry-point subpaths controlled by ng-packagr (a63ebb7)

v13.0.8

Compare Source

v13.0.7

Compare Source

v13.0.6

Compare Source

13.0.6 (2021-11-18)

v13.0.5

Compare Source

13.0.5 (2021-11-17)

v13.0.3

Compare Source

v13.0.2

Compare Source

v13.0.1

Compare Source

v13.0.0

Compare Source

⚠ BREAKING CHANGES
  • TypeScript versions prior to 4.4 are no longer supported.
  • Compilation of libraries using VIew Engine is no longer supported.
  • We no longer generate UMD bundles. The below options which were used for UMD bundle generation has also been removed;
    • umdModuleIds
    • amdId
    • umdId
  • Support for node-sass has been removed. sass will be used by default to compile SASS and SCSS files.
Features
Bug Fixes
Performance
  • only re-generate FESMs when ESM has changed (2a02a89)
  • read esm files from memory (51ba534)
  • store fesm generation state on disk (4565a8b)

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.

@renovate renovate bot force-pushed the renovate/root/ng-packagr-19.x branch from 50904ff to af569b2 Compare November 22, 2024 12:17
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