fix(@angular-devkit/build-angular): update copy-webpack-plugin to v14.0.0

[clydin]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a routine dependency upgrade, specifically updating the copy-webpack-plugin to its latest major version. This update ensures the project benefits from the latest features, bug fixes, and performance improvements offered by the new plugin version. It also aligns the project with updated Node.js compatibility requirements for these dependencies, reflecting a move towards more modern runtime environments.

Highlights

• Dependency Update: The copy-webpack-plugin dependency has been updated from version 13.0.1 to 14.0.0.
• Node.js Engine Requirement: The minimum Node.js engine requirement for copy-webpack-plugin has been raised from 18.12.0 to 20.9.0.
• Transitive Dependency Update: The serialize-javascript dependency, used by copy-webpack-plugin, has been updated from 6.0.2 to 7.0.3, also introducing a higher Node.js engine requirement for it.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• packages/angular_devkit/build_angular/package.json
  • Updated copy-webpack-plugin dependency version to 14.0.0.
• pnpm-lock.yaml
  • Updated the copy-webpack-plugin dependency version to 14.0.0 in the importers section.
  • Updated the copy-webpack-plugin package entry, including its integrity hash and minimum Node.js engine requirement to 20.9.0.
  • Added a new package entry for serialize-javascript@7.0.3 with its Node.js engine requirement of >=20.0.0.
  • Updated copy-webpack-plugin's internal dependency on serialize-javascript to version 7.0.3.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates copy-webpack-plugin to version 14.0.0, which is a major version bump. This update introduces a higher minimum required Node.js version, from >=18.12.0 to >=20.9.0. This is a potentially breaking change for consumers of @angular-devkit/build-angular who are using older, but still supported, versions of Node.js. This needs to be carefully evaluated against the project's Node.js support policy.