You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Snyk] Security upgrade @nrwl/angular from 10.0.12 to 13.0.0 - #1429
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonpackage-lock.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-DECODEURICOMPONENT-21802484
Breaking Change Risk
Important
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)