[Templates] Update SPA dependencies to keep npm audit happy #21330
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.
Description
Many of the node dependencies of SPA project templates have received updates including some security fixes. The current references the SPA project templates have are not up-to-date.
Customer Impact
Customers who create new project will end up using dependencies with known security vulnerabilities. Also, these will result in warnings printed when running newly created SPA projects.
Regression?
These dependencies are not something we have control over. We simply update them from time to time to keep the templates current and in good state.
Risk
Low: The change itself is a low-risk for us as there is no actual functionality change involved in our code.