Skip to content

[Snyk] Security upgrade @nrwl/angular from 10.0.12 to 13.0.0 - #1429

Open
crh225 wants to merge 2 commits into
masterfrom
snyk-fix-5b49d1e919eb63e93dc81656e89be843
Open

crh225 wants to merge 2 commits into
masterfrom
snyk-fix-5b49d1e919eb63e93dc81656e89be843

Conversation

@crh225

@crh225 crh225 commented Oct 29, 2026

Copy link
Copy Markdown
Owner

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
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-DECODEURICOMPONENT-21802484

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


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:

🦉 Regular Expression Denial of Service (ReDoS)

@crh225

crh225 commented Oct 29, 2026

Copy link
Copy Markdown
Owner Author

Merge Risk: High

Upgrading from @nrwl/angular v10 to v13 is a major undertaking that spans three significant Nx versions (v11, v12, v13). This requires a sequential migration, one major version at a time, and involves substantial breaking changes, including updates to Angular, TypeScript, and the core Nx workspace structure.

Key Breaking Changes:

  • Sequential Migration Required: You cannot jump directly from v10 to v13. The recommended path is to migrate one major version at a time (10 -> 11, 11 -> 12, 12 -> 13) using the nx migrate command for each step.
  • Angular and TypeScript Versions: Each major version of Nx has peer dependency requirements for specific versions of Angular and TypeScript. For example, Nx 13 requires Angular 13 and TypeScript 4.4. This will be a significant part of the upgrade process.
  • TSLint to ESLint Migration: Nx v11 and later have deprecated TSLint in favor of ESLint. The migration process will involve converting your linting setup, which can be a complex task.
  • Workspace and Core Package Changes: Starting with Nx 13.10, the core nx package consolidates functionality previously found in @nrwl/cli and @nrwl/tao, simplifying dependencies. Your workspace configuration and scripts will be updated automatically by the migration, but manual verification is crucial.
  • Jest and ES Modules: Nx 13 introduced changes related to ES Modules, which were reported to cause issues with Jest tests in some workspaces.

Recommendation:
This is a high-risk, high-effort upgrade. Do not attempt to merge this change without a dedicated plan. Use the nx migrate command to handle the upgrade one major version at a time. For example, start with nx migrate @nrwl/workspace@11 and follow the instructions, resolving any issues before proceeding to the next major version. Do not use ng update for this process.

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.

2 participants