[Snyk] Fix for 2 vulnerabilities

[ayusuf-mq]

Snyk has created this PR to fix 2 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

• samples/client/petstore/typescript-angular-v7-provided-in-root/package.json
• samples/client/petstore/typescript-angular-v7-provided-in-root/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Cross-site Scripting (XSS) SNYK-JS-ANGULARCOMPILER-14908872	565
	Cross-site Scripting (XSS) SNYK-JS-ANGULARCORE-14908871	565

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Cross-site Scripting (XSS)

[ayusuf-mq]

This is a massive upgrade from Angular 7 to 19, spanning 12 major versions and representing a near-total rewrite of the framework. It requires a complete migration effort, not a simple dependency bump. Key breaking changes include the transition from the legacy View Engine to the Ivy rendering engine, the removal of the Angular Compatibility Compiler (ngcc), and the introduction of standalone components as the new default.

Highlights:

• Ivy Engine: The underlying rendering engine was completely rewritten and became default in v9. Libraries built with the old View Engine are no longer compatible.
• Standalone Components: Since v14 and defaulted in v19, NgModule is no longer required for components, directives, and pipes, fundamentally changing application architecture.

Source: Angular documentation
Recommendation: Do not merge directly. A staged, multi-version migration using the official Angular Update Guide (update.angular.io) is mandatory.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.