## Description
Updates our SPA template dependencies as part of our regular update schedule on patch releases. This update contains an update from Angular 12 to Angular 13.
The update to the angular version has been performed by automation with `ng update`.
## Customer Impact
Templates contain a set of fixed package versions that get regularly out of date and start producing security warnings. As part of our regular patch process we update these dependencies to keep our customers protected and make sure they don't have a bad experience due to security warnings appearing after project creation
## Regression?
- [ ] Yes
- [X] No
## Risk
- [ ] High
- [ ] Medium
- [X] Low
We do this process regularly.
## Verification
- [X] Manual (required)
- [ ] Automated
Validated:
* run Angular Individual auth on windows
* run Angular no auth Individual auth on windows
* run React Individual auth on windows
* run React no auth on windows
* Publish angular individual auth on Windows.
* Publish react individual auth on Windows.
Updating package dependencies is not sensitive to OS issues.
## Packaging changes reviewed?
- [ ] Yes
- [ ] No
- [X] N/A
[Spa] Introduces NoSpaFrontEnd (hidden) option for testing purposes (#15)
In order for us to ensure the templates are up to date with the latest changes on the .NET runtime, we want to have some tests that are able to build them (and run the server part independently) if necessary.
For that matter, we are introducing the NoSpaFrontEnd option which is hidden from the users and that can be specified in tests to remove all integration with the SPA frontend.
We will continue droping the files on disk, but there will be no npm restore during build nor we will try to launch the SPA proxy when the app launches.
We will have some tests on the ASP.NET Core repo that install the templates package produced by the repo and build the templates to at least catch build breaks that changes on ASP.NET Core can cause.
* Get local builds working
- no solution file or build scripts but `dotnet pack` does the trick
- last part of #32027 unless we need Arcade or a CI build urgently
Main work was to add a few missing files and modify them for this environment
- mostly copied from dotnet/aspnetcore
- Directory.Build.props and Directory.Build.targets created from scratch
- some content copied from dotnet/arcade and dotnet/aspnetcore
- NuGet.config and eng/Versions.props copied but pared down (a lot) to mandatory bits for an isolated build
- new eng/ files mostly came from src/ProjectTemplates/ in dotnet/aspnetcore
- eng/DotNetPackageIcon.png came from src/Microsoft.DotNet.Arcade.Sdk/tools/Assets/ in dotnet/arcade
- eng/Packaging.targets copied from src/Microsoft.DotNet.Arcade.Sdk/tools/Workarounds.targets in dotnet/arcade
nits:
- fix whitespace Directory.Build.targets target added to `$(Description)`
- fix typo in the `_AppendRepositoryUrlToPackageDescription` target name
- remove src/.gitignore and move content into new root .gitignore file
- remove SECURITY.md trailing whitespace
* Update templates baseline for recent changes
* Add using alias to fix type name conflict in templates that were missed in the previous set of changes.
* Update SPA templates
- Use top-level statements
- Use minimal hosting APIs
- dotnet/aspnetcore#33947dotnet/aspnetcore#33944
* Fix nullable issue in Blazor Server template
Commit migrated from dotnet/aspnetcore@4cdd594dad
Mackinnon Buck
Marc Gravell
Damian Edwards
Artak
Javier Calvarro Nelson
Daniel Roth
Doug Bunting
Hao Kung
Pranav K
William Godbe
Stephen Halter