Skip to content

Conversation

@patzeltj
Copy link

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json
⚠️ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Cross-site Scripting (XSS)
SNYK-JS-ANGULARCORE-14908871
  651  

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)

@patzeltj
Copy link
Author

Merge Risk: High

This is a major version upgrade across five versions (v14 to v19) that introduces fundamental architectural shifts, new control flow syntax, and requires significant code and environment updates. Direct migration is not feasible; an incremental update (v14→v15, v15→v16, etc.) is required.

Highlights:

  • Standalone Components: The architecture shifts from NgModules to standalone components, which become the default in v17. This changes how components, directives, and pipes are declared and used. [14, 17]
  • New Template Control Flow: Angular v17 introduces a new built-in syntax for control flow (@if, @for) to replace structural directives like *ngIf and *ngFor. [13, 14, 18]
  • View Engine Removal: Support for libraries built with the older View Engine is completely removed in v16 with the deletion of the Angular Compatibility Compiler (ngcc). [9, 15, 23]
  • Environment Updates: Each major version requires specific Node.js and TypeScript versions, with support for older versions being dropped. For example, v17 requires Node.js 18.13.0+ and TypeScript 5.2+. [1, 12, 15]

Source: Angular documentation
Recommendation: Do not attempt a direct upgrade. Follow the official Angular Update Guide to migrate incrementally through each major version. [5, 24, 28]

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

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.

3 participants